chore: Move apache.amber to apache.texera.amber
#4094
Merged
Conversation
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
github-actions
bot
added
engine
python
refactor
…ra.amber This commit refactors the package structure by moving all Amber engine code from org.apache.amber to org.apache.texera.amber. This aligns the package naming with the Texera project organization. - Moved all source directories preserving git history - Updated package declarations in 576 Scala/Java files - Updated import statements across all files - Updated Python proto imports (57 files) - Updated protobuf packages (14 files) - Updated frontend TypeScript imports (2 files) - Updated configuration files (cluster.conf) - Updated string literals with class references for reflection Closes #4003
Yicong-Huang
force-pushed
the
refactor/move-amber-under-texera
branch
from
356a020 to
ea42805
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR performs a large-scale refactoring to migrate the Amber engine codebase from the org.apache.amber package namespace to org.apache.texera.amber. This change aligns the package structure with the Apache Texera project organization and ensures all components are properly namespaced.
Key Changes:
- Migrated all source directories across 8 Scala/Java modules from
org.apache.ambertoorg.apache.texera.amber - Updated package declarations in 576 Scala/Java files
- Updated 57 Python files to use new proto import paths
- Modified 14 Protobuf files with new Java package declarations
- Updated configuration files and string literals containing class names for reflection/dynamic loading
Reviewed changes
Copilot reviewed 293 out of 709 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| cluster.conf | Updated Kryo serializer configuration to reference new package namespace |
| Test files (Scala) | Updated package declarations and imports across all test files |
| Main source files (Scala) | Updated package declarations and imports across engine, architecture, and utility classes |
| Python files | Updated proto imports to reflect new namespace structure |
| WorkerSpec.scala | Updated class name string literal for dynamic loading of DummyOperatorExecutor |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
What changes were proposed in this PR?
This PR refactors the package structure by moving all Amber engine code from
org.apache.ambertoorg.apache.texera.amber. This aligns the package naming with the Texera project organization and ensures all components are properly namespaced under the Apache Texera organization.Key Changes:
Directory Structure Migration - Moved all source directories:
Code Updates - Updated across 707 files:
Package Namespace Changes:
Any related issues, documentation, discussions?
Closes #4003
How was this PR tested?
CI
Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Sonnet 4.5 (Cursor IDE)