Hello,
Due to the nature of NoSQL databases, you generally have to
replicate your data more than once in order to answer different
query patterns. GeoMesa by default will create several indices [1].
However, you can fully control which indices are created [2] if you
want to disable some.
There are some other things you can do as well, such as using
UUID-encoding for feature IDs [3], or TWKB geometry serialization
[4].
Whichever indices you keep, you may also want to look into
configuring HBase to use compression [5].
Thanks,
Emilio
[1]:
https://www.geomesa.org/documentation/user/datastores/index_overview.html
[2]:
https://www.geomesa.org/documentation/user/datastores/index_config.html#customizing-index-creation
[3]:
https://www.geomesa.org/documentation/user/datastores/index_config.html#configuring-feature-id-encoding
[4]:
https://www.geomesa.org/documentation/user/datastores/index_config.html#configuring-geometry-serialization
[5]:
hbase.apache.org/book.html#compression
On 8/14/19 9:31 PM, Yifan Wang wrote:
Hi,
I’m new to Geomesa. I
tried to store data in CSV file to HBase as
SimpleFeatureType. My origin CSV file size was 342M but in
Hbase, the table size was as below.
The structure of SimpleFeatureType was
I am wondering is it normal that the table size
become four times larger than the origin file? Is there
anything I can do to fix this? Thank you!
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________