J'interroge une entité geomesa qui comprend l'index join
sur deux attributs (r
et di
). La requête r=<int-value>
exécute et renvoie des données pour la valeur r
spécifiée, le cas échéant. Cependant, la requête di=<int-value>
ne trouve aucun enregistrement correspondant bien que des enregistrements existent pour le même!Impossible d'interroger avec deux index d'attributs dans le type d'entité geomesa
Voici mon schéma caractéristique:
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'
Je ne suis pas en mesure de trouver la cause racine. Est-ce que je ne peux pas avoir plus d'un index d'attribut dans un schéma?
MISE À JOUR 1
Fixation plan de requête
[2017-05-01 18:51:53,219] TRACE Explainer: Planning 'aj_dev' di = 1
239099 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Planning 'aj_dev' di = 1
[2017-05-01 18:51:53,220] TRACE Explainer: Original filter: di = 1
239100 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Original filter: di = 1
[2017-05-01 18:51:53,220] TRACE Explainer: Hints: density[false] bin[false] stats[false] map-aggregate[false] sampling[none]
239100 [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:51:53,221] TRACE Explainer: Sort: none
239101 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Sort: none
[2017-05-01 18:51:53,221] TRACE Explainer: Transforms: None
239101 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Transforms: None
[2017-05-01 18:51:53,221] TRACE Explainer: Strategy selection:
239101 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Strategy selection:
[2017-05-01 18:51:53,226] TRACE Explainer: Query processing took 3ms and produced 1 options
239106 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Query processing took 3ms and produced 1 options
[2017-05-01 18:51:53,226] TRACE Explainer: Filter plan: FilterPlan[AttributeIndex[di = 1][None]]
239106 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Filter plan: FilterPlan[AttributeIndex[di = 1][None]]
[2017-05-01 18:51:53,226] TRACE Explainer: Strategy selection took 0ms for 1 options
239106 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Strategy selection took 0ms for 1 options
[2017-05-01 18:51:53,226] TRACE Explainer: Strategy 1 of 1: AttributeIndex
239106 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Strategy 1 of 1: AttributeIndex
[2017-05-01 18:51:53,226] TRACE Explainer: Strategy filter: AttributeIndex[di = 1][None]
239106 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Strategy filter: AttributeIndex[di = 1][None]
[2017-05-01 18:51:53,227] TRACE Explainer: Plan: org.locationtech.geomesa.accumulo.index.EmptyPlan
239107 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Plan: org.locationtech.geomesa.accumulo.index.EmptyPlan
[2017-05-01 18:51:53,227] TRACE Explainer: Table:
239107 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Table:
[2017-05-01 18:51:53,227] TRACE Explainer: Deduplicate: false
239107 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Deduplicate: false
[2017-05-01 18:51:53,227] TRACE Explainer: Column Families: all
239107 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Column Families: all
[2017-05-01 18:51:53,228] TRACE Explainer: Ranges (0):
239108 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Ranges (0):
[2017-05-01 18:51:53,228] TRACE Explainer: Iterators (0):
239108 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Iterators (0):
[2017-05-01 18:51:53,228] TRACE Explainer: Plan creation took 1ms
239108 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Plan creation took 1ms
[2017-05-01 18:51:53,228] TRACE Explainer: Query planning took 17ms
239108 [Thread-5] TRACE org.locationtech.geomesa.index.utils.Explainer - Query planning took 17ms