question

Hi @raktim.0526_188212

I see from the comments that your follow-on questions moved to filter queries with Gremlin, away from geospatial queries.

To do the equivalent of a filter query on the solr index with gremlin, you would construct your gremlin statement like this:

g.V().hasLabel("mylabel") //this identifies the vertex table and solr core
   .has("property_name", "search_term") //this is the filter query equivalent
   .valueMap() //this gives you all the properties for the returned vertices

Using the .profile() step in the gremlin query allows you to see how the query is translated to cql and what solr query is used:

Here is an example from a test graph:

gremlin> g.V().hasLabel("product").has("product_colour", "red").valueMap().profile()
==>Traversal Metrics
Step                                                               Count  Traversers       Time (ms)    % Dur
=============================================================================================================
__.V().hasLabel("product").has("product_colour"...                   315         315          40.207    93.91
  CQL statements ordered by overall duration                                                  34.226
    \_1=SELECT * FROM products2.product WHERE solr_query = '{"q":"*:*", "fq":["product_colour:red"]}' LIMIT 2
        147483647 / Duration: 34 ms / Count: 1
HasStep([~label.eq(product), product_colour.eq(...                   315         315           0.688     1.61
PropertyMapStep(value)                                               315         315           0.911     2.13
ReferenceElementStep                                                 315         315           1.008     2.35
                                            >TOTAL                     -           -          42.815        -

For documentation on using a search index in Gremlin queries, see here:

https://docs.datastax.com/en/dse/6.8/dse-dev/datastax_enterprise/graph/using/useIndexes.html

To do a groupCount (like a facet count) on the property, you can do the following. Note that this does not use the search index:

gremlin> g.V().hasLabel("product").groupCount().by("product_colour")
==>{magenta=309, pink=311, yellow=332, turquoise=351, cyan=334, gold=324, red=315, fuchsia=313, white=305, olive=322, ivory=318, lavender=318, azure=340, plum=291, tan=301, green=352, mint green=303, lime=338, salmon=306, black=333, violet=324, teal=334, grey=304, orange=346, blue=334, sky blue=329, purple=334, silver=320, indigo=328, maroon=302, orchid=329}


gremlin> g.V().hasLabel("product").groupCount().by("product_colour").profile()
==>Traversal Metrics
Step                                                               Count  Traversers       Time (ms)    % Dur
=============================================================================================================
__.V().hasLabel("product")                                         10000       10000         116.203    89.79
  CQL statements ordered by overall duration                                                   5.257
    \_1=SELECT * FROM products2.product / Duration: 5 ms / Count: 1 / Index type: Table: product
HasStep([~label.eq(product)])                                      10000       10000           4.746     3.67
GroupCountStep(value(product_colour))                                  1           1           8.370     6.47
ReferenceElementStep                                                   1           1           0.100     0.08
                                            >TOTAL                     -           -         129.420        -