Updated README#3382
Open
priyanshi-yb wants to merge 1 commit into
Open
Conversation
| - Live migration of Oracle databases with fall-forward and fall-back. | ||
| - Direct data import from CSV or TEXT format files on local disk or cloud storage. | ||
| - Parallelism of data across tables and within tables. | ||
| - Auto-tuneable based on workloads, by analyzing the target cluster capacity. |
Collaborator
There was a problem hiding this comment.
I like the "Optimized for distributed databases" category. SHall we keep that?
| - [YugabyteDB Anywhere](https://docs.yugabyte.com/preview/yugabyte-platform/create-deployments/) | ||
| - [YugabyteDB Aeon](https://docs.yugabyte.com/preview/yugabyte-cloud/cloud-basics/) | ||
|
|
||
| # Current Product State and Roadmap |
Collaborator
There was a problem hiding this comment.
IMO, better to run this by Hemant/AV.
Should be okay to remove as this is outdated, but we should at least discuss if we want to have an updated one, or it's fine.
| For detailed version compatibility across migration types, refer to the [target database documentation](https://docs.yugabyte.com/preview/yugabyte-voyager/introduction/#target-database). | ||
|
|
||
| <img src="docs/voyager_current_state_and_roadmap.png" align="center" alt="YugabyteDB Voyager Architecture"/> | ||
| ## Migration Types |
Collaborator
There was a problem hiding this comment.
Should this come after Migration Workflow below? And maybe let's call it "Data Migration Types/Workflows"?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe the changes in this pull request
Describe if there are any user-facing changes
How was this pull request tested?
Does your PR have changes in callhome/yugabyted payloads? If so, is the payload version incremented?
Does your PR have changes to on-disk structures that can cause upgrade issues?
Reference
On-disk structures potentially causing breaking changes:
Note
Low Risk
Documentation-only updates (README/release notes link) with no code-path or behavioral changes; main risk is stale/incorrect links or installation commands.
Overview
Updates
README.mdto be a more complete entrypoint: adds a Table of Contents, rewrites the feature list, documents supported source/target databases and migration types, and adds explicit prerequisites, installation methods (brew/apt/yum/docker/source/airgapped), and a step-by-step migration workflow with updated documentation links.Updates
RELEASE_NOTES.mdto point readers to the official documentation for the latest release notes.Written by Cursor Bugbot for commit 2c77a16. This will update automatically on new commits. Configure here.