Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geomesa-dev] Unable to query with two attribute indexes in geomesa feature type
Hi Emilio

Here is the log for query di = 1: 

[2017-05-01 18:47:54,120] TRACE Explainer: Planning 'aj_dev' di = 1

0 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  - Planning 'aj_dev' di = 1

[2017-05-01 18:47:54,124] TRACE Explainer:   Original filter: di = 1

4 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -   Original filter: di = 1

[2017-05-01 18:47:54,128] TRACE Explainer:   Hints: density[false] bin[false] stats[false] map-aggregate[false] sampling[none]

8 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -   Hints: density[false] bin[false] stats[false] map-aggregate[false] sampling[none]

[2017-05-01 18:47:54,131] TRACE Explainer:   Sort: none

11 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -   Sort: none

[2017-05-01 18:47:54,134] TRACE Explainer:   Transforms: None

14 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -   Transforms: None

[2017-05-01 18:47:54,135] TRACE Explainer:   Strategy selection:

15 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -   Strategy selection:

[2017-05-01 18:47:54,203] TRACE Explainer:     Query processing took 60ms and produced 1 options

83 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -     Query processing took 60ms and produced 1 options

[2017-05-01 18:47:54,210] TRACE Explainer:     Filter plan: FilterPlan[AttributeIndex[di = 1][None]]

90 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -     Filter plan: FilterPlan[AttributeIndex[di = 1][None]]

[2017-05-01 18:47:54,211] TRACE Explainer:     Strategy selection took 5ms for 1 options

91 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -     Strategy selection took 5ms for 1 options

[2017-05-01 18:47:54,212] TRACE Explainer:   Strategy 1 of 1: AttributeIndex

92 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -   Strategy 1 of 1: AttributeIndex

[2017-05-01 18:47:54,213] TRACE Explainer:     Strategy filter: AttributeIndex[di = 1][None]

93 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -     Strategy filter: AttributeIndex[di = 1][None]

[2017-05-01 18:47:54,235] TRACE Explainer:     Plan: org.locationtech.geomesa.accumulo.index.EmptyPlan

115 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -     Plan: org.locationtech.geomesa.accumulo.index.EmptyPlan

[2017-05-01 18:47:54,236] TRACE Explainer:       Table: 

116 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -       Table: 

[2017-05-01 18:47:54,238] TRACE Explainer:       Deduplicate: false

118 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -       Deduplicate: false

[2017-05-01 18:47:54,239] TRACE Explainer:       Column Families: all

119 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -       Column Families: all

[2017-05-01 18:47:54,241] TRACE Explainer:       Ranges (0): 

121 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -       Ranges (0): 

[2017-05-01 18:47:54,244] TRACE Explainer:       Iterators (0):

124 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -       Iterators (0):

[2017-05-01 18:47:54,246] TRACE Explainer:     Plan creation took 21ms

126 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -     Plan creation took 21ms

[2017-05-01 18:47:54,247] TRACE Explainer:   Query planning took 200ms

127 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer  -   Query planning took 200ms

Thank You

Suresh Prajapati


On Mon, May 1, 2017 at 6:37 PM, Emilio Lahr-Vivaz <elahrvivaz@xxxxxxxx> wrote:
Hi Suresh,

You can have more than one indexed attribute. Can you provide the explain logging for your query? That's usually the first place to look when a query isn't behaving like you expect.

Thanks,

Emilio


On 05/01/2017 08:09 AM, Suresh Prajapati wrote:
Hello Everyone

I am querying a geomesa feature which includes join index on two attributes(r and di). Query r=<int-value> runs and returns data for specified r value if any. However Query di=<int-value> doesn't finds any matching records though records for the same exists!

Here is my feature schema:

r:Long:cardinality=high:index=join,*g:Point:srid=4326,di:Integer:index=join,al:Float,s:Float,b:Float,an:Float,he:Float,ve:Float,t:Float,m:Boolean,i:Boolean,ts:Long;geomesa.table.sharing='true',geomesa.indices='attr:4:3,records:2:3,z2:3:3',geomesa.table.sharing.prefix='\\u0001'

I am not able to find out the root cause. Can't i have more than one attribute index in one schema?

Thank You

Suresh Prajapati



_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-dev


_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-dev

Back to the top