-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Error creating index (error on compacting) #1844
Comments
Counting should be instantaneous, unless you have a WHERE condition. About the compaction error, could you please try to rebuild the index with the |
Hi. Rebuilding the index keeps throwing the same errors...
Counting from Console is indeed instantaneous:
But same count on Studio, it takes several minutes. On this case, server logs:
|
Commands executed from Studio are adding a default limit to avoid the browser crashes with thousands or more records to render. For this reason, I think the optimizer is not smart enough and it simply scans the whole type. It's a bug, checking into the code. |
About the compaction error, I'd love to have those files. Is it possible to have zipped? |
I can share you a reduced version of the database where the error can be replicated. Where or how do I send it to you? |
Could you please send it to support at arcadedata dot com? Thanks! |
ArcadeDB Version:
24.11.1 (ArcadeDB Server v24.11.1 (build b466f48/1730841732933/main))
OS and JDK Version:
Ubuntu 24.10, JDK 21.0.5 (Linux 6.11.0-8-generic - OpenJDK 64-Bit Server VM 21.0.5 (Temurin-21.0.5+11))
Expected behavior
To create an index successfully (with SQL
create index on Type(prop) notunique
).Actual behavior
I have a document type AuditLog with 135+ millions of documents, when I execute create index sentence on a property, in the server logs several times it logs something like this:
The process continues despite the errors. When I run a select that would use the index, the server logs:
Steps to reproduce
I dont't know if it's occurred because of something in the data or why.
Note:
Running
select count(*) from Type
on a type with millions of documents, is very slow... on my AuditLog type previously mentioned, counting documents takes several minutes... is this slow counting so by design?The text was updated successfully, but these errors were encountered: