-
Notifications
You must be signed in to change notification settings - Fork 871
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
Distributed: asynchronous inserts ignore unique indexes #2914
Comments
Fixed in 9804c47 and deployed in last 2.0-SNAPSHOT. |
The issue is again present in version 2.0.9, 2.0.12. Whilst the index is created, it is ignored during insert in distributed mode. Once duplicates have been inserted, rebuilding the index will cause an exception as expected. |
I cannot reproduce it. Do you have a test case? |
|
Thanks, working on it... |
Reproduced with a Java test case. |
@lvca This is still the case with 2.1.6. |
@testark Could you please look at test case https://github.com/orientechnologies/orientdb/blob/ad0e676ffcae25f13e9a67cc58d9a232e6c07fe1/distributed/src/test/java/com/orientechnologies/orient/server/distributed/asynch/AsyncIndexTest.java#L41-L40? It passes with no problems. |
Created new test case (e2b40ee) with 3 servers and remote and pass... |
The test case deals with the document API. I'm using the Graph API. |
You're right, I was able to reproduce it with 3 nodes, async replication through remote protocol call and graph API that always start a distributed transaction. Working to the fix. |
@lvca See? :-) I was not trying to be mean or something, just reporting because it is still indeed the case. Glad you can work on that. |
Fixed in 2.1.x |
Applying a unique index such as
"create index sms_keys ON SMS (type, lang) unique"
is ignored during inserts in distributed asynchronous mode.
The text was updated successfully, but these errors were encountered: