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

Support CCL search operators #511

Open
jtnelson opened this issue Apr 29, 2024 · 5 comments
Open

Support CCL search operators #511

jtnelson opened this issue Apr 29, 2024 · 5 comments

Comments

@jtnelson
Copy link
Member

Support cinchapi/ccl#42

When search operators are included, query logic should leverage search() functions

@jtnelson
Copy link
Member Author

To implement,

private boolean is(BiFunction<TObject, TObject, Integer> comparer,
: Add support for search operators

public Map<Long, Set<TObject>> explore(String key, Aliases aliases) {
: Check if operator is a search operator and defer to the search call?

@jtnelson
Copy link
Member Author

Need to have a fallback for timestamp queries with search operators. So, in the Database will need to support the search operators in the IndexRecord#findAndGet.

@jtnelson
Copy link
Member Author

I think find is the only Store routine that calls into explore. If so, get rid of explore and just implement the logic in find directly. This will make it easy to call into the search method in the Database when trying to respond to a search operator

@jtnelson
Copy link
Member Author

jtnelson commented May 1, 2024

https://github.com/cinchapi/concourse/blob/develop/concourse-server/src/main/java/com/cinchapi/concourse/server/query/Finder.java#L129

An alternative is to add logic in Finder to check if the operator is a search operator and therefore defer to the engine search method. This will mean we can't support historical search

@jtnelson
Copy link
Member Author

jtnelson commented May 1, 2024

^^^ that won't work for navigation keys though

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

No branches or pull requests

1 participant