Andrzej Liszka

not sure issue still exists, but commits references above are related to gh-1821. made a typo in issue number (https://github.com/weaviate/weaviate/pull/1862)

Thank @samos123 for reporting the issue and a reproducible example. I can confirm that weaviate returns rounded numbers and your suspicion is correct. While int64 values are stored correctly, it...

Thank you @codebrain for reporting the issue. That is true, fields are not used in java client, though along with `query`, `operationName` and `variables` are part of GraphQL spec and...

Thank you @MinyShrimp for reporting the issue. Indeed `@EqualsAndHashCode` annotation is missing in multiple data classes. We will add it soon. As for `@Singular` annotation: it definitely is a nice...

Thank you @codebrain for reporting the issue. Indeed those 2 values are not set. They seem to be leftovers of non-existent functionality. We will remove them from clients and weaviate...

Thank @samos123 for reporting the issue. You are right, Double is not suitable for holding int64 numbers like given `9223372036854775807` (as it is rounded to `9223372036854776000`) and Long would fit...

Hey @varshith257, could you please fix warnings listed by GH on `Files changed` tab? `lsmkv.CursorMap` now needs `context` as 1st argument in his methods. Also `RowReaderRoaringSet::notLike()` is not defined. Thank...

Hey @varshith257, after running pipelines it turns out unit tests fail. Could you look into them? `TestRowReaderRoaringSet/not_like_'h*'_value` `TestRowReaderRoaringSet/not_like_'h*'_value_with_3_results_limit` Thank you!

closing for now, as migration might be not needed.

changes merged to 1.31 and later (https://github.com/weaviate/weaviate/pull/8632) skipping merge to 1.30