-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Base64 encode compaction input file list #5229
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May not want to pass data through toString as that could corrupt binary data. It would be nice if we could use the internal class and machinery in StoredTabletFile here, but as @cshannon mentioned that would break encapsulation. Encapsulation is nice and I would not want to see StoredTabletFile internals in my ide when doing completion, we could break encapsulation in a limited way possibly by doing the following.
o.a.a.c.metadata
and the other is ino.a.a.c.metadata.schema
.This way most of the Accumulo code can not see StoredTabletFile.TabletFileCqMetadataGson and we still get a nice human readable encoding maybe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
path
andrange
are defined inAbstractTabletFile
. Can we just move the serialization and deserialization methods, andTabletFileCqMetadataGson
there and make them public?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO it would be nice to avoid making them public. I was thinking some package private methods like the follow could be added to StoredTabletFile in addition to making TabletFileCqMetadataGson package private. Could refactor the code in StoredTabletFile to accomodate and or use these methods.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When i first looked into this issue and I mentioned that we would break encapsulation I should have elaborated that I was referring to TabletFileCqMetadataGson being private and that the StoredTabletFile kept all of that internal so I didn't want to expose it.
I agree with @keith-turner that if we at least make the code around the serialization package protected and not public that would be a good compromise I think. The TabletFileCqMetadataGson would certainly be the thing to re-use here because it already handles everything correctly with encoding/decoding the binary ranges so no need to have to do it again.
One other nice benefit of making TabletFileCqMetadataGson and the serialization code for it package protected instead of private is that it would be easier to write some unit tests if we wanted.