-
Notifications
You must be signed in to change notification settings - Fork 32
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
Double index problems? #135
Comments
Hi @rtfpessoa should be related in composite indexing usage. Let me check |
Hi @rtfpessoa how did you create the class? |
Should be this:
|
btw a colleague just found that this problem only happens with index type |
Apparently the query only works if I also use both the filters of the index. If I do a query on only one of the index params it will fail. Do you have any news? |
Hi @rtfpessoa that's because the hash index cannot be used in order to do lookup with partial key. |
@maggiolo00 but even with Just to make this clear. If I have some queries that do not want to use the index how can I do it? |
hi @rtfpessoa do you get the same exception with I don't think you can remove the Optimization Step per query but let me check |
We tested with unique and I also get that problem. |
Also when we use
|
I am having problems running this query:
when I have an index like this:
it seems that he is trying to convert the value of the second field of the index to the type of the first element of the index giving this exception:
If I change the index to:
The error changes to:
I noticed this two (#126 #110) similar issues but not sure if it can be the same problem.
Any ideas what can be wrong?
The text was updated successfully, but these errors were encountered: