Skip to content
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

Remove TableLayout from Accumulo connector #823

Merged
merged 1 commit into from
Jun 4, 2019

Conversation

Praveen2112
Copy link
Member

Removes the TableLayout for Accumulo connector. (#781)

@cla-bot cla-bot bot added the cla-signed label May 27, 2019
@martint martint self-requested a review May 31, 2019 05:53
@Praveen2112 Praveen2112 force-pushed the accumulo_table_layout_removal branch from bdff503 to f023b4e Compare June 1, 2019 13:04
handle.getTable(),
handle.getRowId(),
newDomain,
getColumnConstraints(handle.getRowId(), newDomain),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to hold on to the column constraints in the table handle? It seems like we should be able to do this directly where they are needed (i.e., in getSplits)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Column constraints are also similar to TupleDomain which would remain same for all splits so thought of moving it to the AccumuloTableHandle.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I can tell, they are only used in getSplits() to call client.getTabletSplits(...), but they are not stored in splits. So we could derive them directly in getSplits() from the information in the handle.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was passed to AccumuloRecordSet and AccumuloRecordCursor but it is not used anywhere expect in getting the split metadata. So we can maintain it as TupleDomain and derive it from table handle.

@Praveen2112 Praveen2112 force-pushed the accumulo_table_layout_removal branch from f023b4e to 6b38abc Compare June 4, 2019 06:14
@Praveen2112 Praveen2112 force-pushed the accumulo_table_layout_removal branch from 6b38abc to f86bcb7 Compare June 4, 2019 06:19
@Praveen2112
Copy link
Member Author

@martint Have removed the column constraint from the table handle. Please let me know if there is any more changes.

Copy link
Member

@martint martint left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I'll merge it once Travis passes.

@martint martint added this to the 314 milestone Jun 4, 2019
@martint martint merged commit 435329d into trinodb:master Jun 4, 2019
@Praveen2112 Praveen2112 deleted the accumulo_table_layout_removal branch July 24, 2019 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants