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

Add support for solr predicates #4

Closed
wants to merge 2 commits into from
Closed

Conversation

paulcwarren
Copy link
Collaborator

Add support for solr predicates

@tgeens tgeens self-requested a review August 16, 2021 06:23

public class SolrUtils {

public static String from(ThunkExpression<Boolean> thunk/*, PathBuilder<?> entityPath*/) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Does the SolrConverter not need to know for which entity we're doing a query ? The thunks/expressions use entity as a placeholder, but is only applied on a specific entity.

In the querydsl implementation, this information is captured in this PathBuilder<?>.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

No, I don't think so. From the looks of the querydsl converter you need to know the subject in order to build a "correct" predicate expression.

In solr, additional sync'ed attributes are under the control of the application actually and its there where the attributes are defined (by defining an AttributeProvider bean). So, actually, I am not even sure this solr converter should be part of the set of thunx libraries. It should probably just be code in the application, or an application library.

@tgeens
Copy link
Contributor

tgeens commented Sep 10, 2021

"So, actually, I am not even sure this solr converter should be part of the set of thunx libraries. It should probably just be code in the application, or an application library."

So euhm, should we hold off merging this ?

@paulcwarren
Copy link
Collaborator Author

Let's close this as it seems we both agree that this should be an application level addition.

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.

2 participants