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

Changes for indexing option - create collection and cache #771

Merged
merged 6 commits into from
Jan 8, 2024

Conversation

maheshrajamani
Copy link
Contributor

@maheshrajamani maheshrajamani commented Jan 5, 2024

What this PR does:
Added the option to provide fields for indexing - allowed or denied
Add the indexing option to cache

Which issue(s) this PR fixes:
Fixes #765 #766

Checklist

  • Changes manually tested
  • Automated Tests added/updated
  • Documentation added/updated
  • CLA Signed: DataStax CLA

@maheshrajamani maheshrajamani requested a review from a team as a code owner January 5, 2024 16:59
type = SchemaType.ARRAY,
implementation = String.class)
@Nullable
List<String> deny) {}
Copy link
Contributor

Choose a reason for hiding this comment

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

As per my note below, I think validation could be encapsulated within config class itself; either in (canonical) constructor, or, maybe cleaner, in a create(...) method that verifies everything is good (and if not throws exception), then calls canonical constructor.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thought about it., For this need to create separate validators to verify things like either one of the field can only be used. So decided to do it as part of resolver.

Copy link
Contributor

Choose a reason for hiding this comment

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

By validator I didn't mean anything pluggable or related to Quarkus.

Copy link
Contributor

@tatu-at-datastax tatu-at-datastax 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 overall, added some suggestions for refactoring.

@maheshrajamani maheshrajamani self-assigned this Jan 5, 2024
@tatu-at-datastax
Copy link
Contributor

Ok, I'll read through everything once more (in a bit, offline for an hour), to make sure I get the overall thing right.
I think I missed some aspects.

Copy link
Contributor

@tatu-at-datastax tatu-at-datastax left a comment

Choose a reason for hiding this comment

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

Ok looks good, thank you for taking time to explain where I misunderstood code & constraints.

Added some suggestions as usual; nothing major.

@maheshrajamani maheshrajamani merged commit 587a6b9 into main Jan 8, 2024
2 checks passed
@maheshrajamani maheshrajamani deleted the indexing-options-meta-data branch January 8, 2024 16:24
@maheshrajamani maheshrajamani restored the indexing-options-meta-data branch January 8, 2024 17:07
@maheshrajamani maheshrajamani deleted the indexing-options-meta-data branch January 8, 2024 17:07
Copy link
Collaborator

@vkarpov15 vkarpov15 left a comment

Choose a reason for hiding this comment

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

LGTM 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Indexing options] Create collection changes to add indexing options
4 participants