orientechnologies / orientechnologies/orientdb
.size() function gives wrong value
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5k
- Forks
- 868
- Avg merge
- 15h 6m
- Merged PRs (30d)
- 18
Description
OrientDB Version: 3.2.5
Java Version: 8
OS: Windows server 2019
Decided to upgrade orient from 3.0.29 to 3.2.5.
It seems that in new version the size() function give a wrong answer.
I don't know if it is a fail import with some corupted data, ai tried repair database but no problem found, also maybe libked with -> https://github.com/orientechnologies/orientdb/issues/9767
Expected behavior
Actual behavior
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported size() behavior in OrientDB 3.2.5 and comparing it with 3.0.29 using the supplied Windows Server 2019 and Java 8 context. Inspect the screenshots and related issue #9767 for more precise reproduction details, then determine whether the result is caused by import corruption or query behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100