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

Predicate optimisation #9

Open
neilstevenson opened this issue Oct 17, 2016 · 6 comments
Open

Predicate optimisation #9

neilstevenson opened this issue Oct 17, 2016 · 6 comments

Comments

@neilstevenson
Copy link
Contributor

(Migrated issue from https://github.com/hazelcast-incubator/spring-data-integrations-commons/issues/18)

In org.springframework.data.hazelcast.repository.query.HazelcastPartTreeQuery, the execute() method calls prepareQuery() on each invocation.

If a query is reused, as most are, this is unnecessary parsing. Some sort of parameter binding mechanism could be more efficient.

@dbrimley
Copy link

dbrimley commented May 2, 2018

We might need a predicate binding on the hazelcast side (cc @gokhanoner )

@gokhanoner
Copy link
Contributor

@dbrimley I believe we can open a Hazelcast issue, refer here & close this one.

@leszko
Copy link

leszko commented Nov 30, 2018

Is it still a valid GH Issue? @neilstevenson @dbrimley @gokhanoner

@gokhanoner
Copy link
Contributor

@leszko, as mentioned, we can open an issue on hazelcast for query binding & close this one since it need to be resolved in hazelcast-core

@pivovarit
Copy link
Contributor

@neilstevenson can this one be closed already?

@mesutcelik
Copy link
Contributor

@pivovarit as suggested above, Can you create an issue on hazelcast and close this one?

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

No branches or pull requests

6 participants