R-tree serialization support

[pomadchin]

R-tree serialization could be a pretty nice extra feature to support as a part of this fantastic tiny library.

• Link to a Java library that has some R-tree serialization implementations to inspire

Is there any interest in such kind of functionality support, or that was intentionally not implemented? Could be nice to establish / contribute into some sort of a standard for the R-tree serialization format (if there is no such yet).

// definitely a feature request / enhancement / help wanted issue

[plokhotnyuk]

Hi, Grigory!

I understand that building R-tree can be faster from serialized form, but it will require serialization of all user's entries.

Could you please, describe your case with more context to avoid XY problem?

[pomadchin]

Hi Andriy,

Thanks for replying that fast!

The use case is in building an index for the parquet file of geometries and persisting it, so we are not rebuilding it every time. The leafs of a tree will contain file block id(s) which later on can be used to perform reads.

I don’t need serialization immediately (it was resolved in a bit different fashion, I can tell you more but it seems like the out of scope conversation) and also don’t have any capacity to work on it.

But conceptually the idea of an efficient persistent index is of a significant interest to me: I have a feeling that such index may work way faster than the inbuilt parquet reader predicates api; I could also be wrong since that’s unclear what benefits we really get with it until we try, the cons are obvious though.