|Re: [geowave-dev] Accumulo Tables|
Okay. It´s for evaluation purposes. Because Geomesa splits these data in multiple tables these values would be a good comparison for disk usage between Geomesa and GeoWave.
Date: Wed, 30 Sep 2015 11:55:29 -0400
Subject: Re: [geowave-dev] Accumulo Tables
That is correct, the data and the index are colocated in the same table. To get a better idea for how this works out, check out our Accumulo Key Structure here. Looking at that, you'll see that each key value pair is composed from a variety of elements, including the Index ID (i.e. the geospatial index), feature field id (column qualifier) and the feature field value.Can I ask why you would want to separate the data from the index? It seems to me that if you took that approach, you would have a secondary geospatial index instead of the primary geospatial index that we provide. By separating the data from the index, that would mean that when running spatial queries, there would be an additional hop to retrieve your actual data. By creating a primary geospatial index (where the data is colocated with the index), there are no additional hops needed to retrieve your data when running a spatial query.
Does that make sense?
On Wed, Sep 30, 2015 at 10:36 AM, Marcel <m.jacob@xxxxxxxxxxx> wrote:
_______________________________________________ geowave-dev mailing list geowave-dev@xxxxxxxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.locationtech.org/mailman/listinfo/geowave-dev
Back to the top