Migrator Service
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
If someone is looking to migrate to Ambry after trying out other options, they might have some files on-premise or some other object store. So, definitely they might be looking to migrate those to ambry in a simpler manner. Would be great if we have a migrator service.
Some requirements for a migrator service:
1. Given a root directory, the migrator service should upload all files to ambry and return a map of file names(with paths) to AmbryIds.
2. Define an interface so that the migrator service can poll a service for objects and uploads to ambry. For instance, from hdfs or amazon S3.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files, tests, or entry points are named. Start by locating Ambry's existing upload and service boundaries, then define how a root-directory migration returns file paths mapped to AmbryIds and how polling sources such as HDFS or Amazon S3 fit the interface. Done means the stated migration and polling requirements have an agreed, tested implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100