Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geomesa-users] Which(Date or Long) type to use for storing timestamp values
Hi Suresh,

It depends on your query patterns. If you use the default date index, you will get a combined geometry + date index (z3 or xz3), which should perform well for spatio-temporal queries, and decently for temporal only queries. If you create an attribute index on your date (either as a date or long type, functionally it makes no difference), then that index will work better for temporal only queries.

Thanks,

Emilio

On 05/15/2017 08:02 AM, Suresh Prajapati wrote:
Hello Everyone,

I am using geomesa for indexing over acccumulo storage. I have an attribute which stores timestamp values. I am confused between which TYPE and INDEX to use for storing timestamp attribute values depending upon performance.

There are two cases

 1. Using `Long` as timestamp type and create attribute index.
 2. Using `Date` type and use default date index.

I want to know which technique is better out of this two in terms of searching and sorting in millions of records. What is best practice to follow? 

Thank You/
Suresh Prajapati


_______________________________________________
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

Back to the top