Same Gremlin Query not returning data after migrating from 3.2.18-tp3 to 3.2.39-tp3

[VishnuAmritanshu]

Recently i have migrated from orient DB 3.2.18-tp3 to 3.2.39-tp3.
In one of my application I am making below gremlin query to return the data. Issue is with 3.2.18-tp3 gremlin query returning the data but with 3.2.39-tp3 empty data result coming.

Gremlin Query:
g.V().hasLabel('object_model').as('m').has('s_model','abc.iaTest.some.engineering').has('p_models.abc_test_amxyz_assetCriticality.typeId','AssetCriticalityTypeBModel')

Any advised what causing the issue? how to trouble shoot and fix it.

[tglman]

Hi,

Not sure what could be the cause for this problem, I will double check the diff to see what has been changed between versions, I got one question when doing has('p_models.abb_ability_am_assetCriticality.typeId','AssetCriticalityTypeBModel') is p_models.abb_ability_am_assetCriticality.typeId a property name or is navigating trough embedded/linked properties ?
bye

[VishnuAmritanshu]

In the raw Json result value look like below. seems like a flat property with dot notations in between
"'p_models.abc_test_amxyz_assetCriticality.typeId": "AssetCriticalityTypeBModel",

is there any changes in between Orientdb version 3.2.18 and 3.2.27 where how orientDB processed and traversed through dynamic properties ( with dot notations ) has been changed??

We tried migrating and updating to version 3.2.32, 3.2.39, 3.2.43, 3.2.27 but at every version we facing the same issue.

when we break the query and running

g.V().hasLabel('object_model').as('m').has('s_model','abc.iaTest.some.engineering') -- this is returning record

g.V().hasLabel('object_model').as('m').has('s_model','abc.iaTest.some.engineering').has('p_models.abc_test_amxyz_assetCriticality.typeId','AssetCriticalityTypeBModel') --- no record

[VishnuAmritanshu]

FYI we using below gremin-server.yaml. Does adding any scriptEngines/serializers could tackle this issue

host: 0.0.0.0
port: 8182
evaluationTimeout: 6000000
channelizer: org.apache.tinkerpop.gremlin.server.channel.WebSocketChannelizer
graphManager : com.orientechnologies.tinkerpop.server.OrientGremlinGraphManager
graphs: {
  graph : ../config/orientdb-im.properties
}
scriptEngines: {
  gremlin-groovy: {
    plugins: { org.apache.tinkerpop.gremlin.server.jsr223.GremlinServerGremlinPlugin: {},
               org.apache.tinkerpop.gremlin.orientdb.jsr223.OrientDBGremlinPlugin: {},
               org.apache.tinkerpop.gremlin.jsr223.ImportGremlinPlugin: {classImports: [java.lang.Math], methodImports: [java.lang.Math#*]},
               org.apache.tinkerpop.gremlin.jsr223.ScriptFileGremlinPlugin: {files: [../config/demodb.groovy]}}}}
serializers:
  - { className: org.apache.tinkerpop.gremlin.util.ser.GraphSONMessageSerializerV3, config: { ioRegistries: [org.apache.tinkerpop.gremlin.orientdb.io.OrientIoRegistry] }}         # application/json
processors:
  - { className: org.apache.tinkerpop.gremlin.server.op.session.SessionOpProcessor, config: { sessionTimeout: 28800000 }}
  - { className: org.apache.tinkerpop.gremlin.server.op.traversal.TraversalOpProcessor, config: { cacheExpirationTime: 600000, cacheMaxSize: 1000 }}
metrics: {
  consoleReporter: {enabled: true, interval: 180000},
  csvReporter: {enabled: true, interval: 180000, fileName: /tmp/gremlin-server-metrics.csv},
  jmxReporter: {enabled: false},
  slf4jReporter: {enabled: false, interval: 180000}}
strictTransactionManagement: false
maxInitialLineLength: 4096
maxHeaderSize: 8192
maxChunkSize: 8192
maxContentLength: 1048576
maxAccumulationBufferComponents: 1024
resultIterationBatchSize: 64
writeBufferLowWaterMark: 32768
writeBufferHighWaterMark: 1048576
authentication: {
  authenticator: com.orientechnologies.tinkerpop.server.auth.OGremlinServerAuthenticator
    }
ssl: {
  enabled: false}

threadPoolWorker: 8
gremlinPool: 32

[VishnuAmritanshu]

One more observation which wanted to share with you. Currently we using Orientdb Version 3.2.18, I downgraded Orientdb version to 3.2.17.

g.V().hasLabel('object_model').as('m').has('s_model','abc.iaTest.some.engineering').has('p_models.abc_test_amxyz_assetCriticality.typeId','AssetCriticalityTypeBModel')

Above query worked with 3.2.17 & 3.2.18 but not working with 3.2.19. Something breaking in between migration from 3.2.18 to 3.2.19

[tglman]

Hi,

Thanks are you sure that the fault is in 3.2.18 -> 3.2.19 ? I do not have many changes there, instead 3.2.17 -> 3.2.18 the gremlin version was updated https://github.com/orientechnologies/orientdb-gremlin/commits/3.2.18 (specific commit orientechnologies/orientdb-gremlin@04a5163) which may introduce some integration issue

[VishnuAmritanshu]

Strange, Not sure but it's working fine when migrating from 3.2.18 to 3.2.17 and backforth. But issue started coming with as I migrate to >=3.2.19

One more observation in 3.2.32, if I create a new record and in property name use "@" instead of "." , it's working for me.

g.V().hasLabel('object_model').as('m').has('s_model','abc.iaTest.some.engineering').has('**p_models.abc_test_amxyz_assetCriticality.typeId**','AssetCriticalityTypeBModel') - **no record**

g.V().hasLabel('object_model').as('m').has('s_model','abc.iaTest.some.engineering').has(**'p_models@abc_test_amxyz_assetCriticality@typeId1**','AssetCriticalityTypeBModelTest||RenamingTypeIdToTypeId1||Value2') - **record getting returned**

Also when I replace the "has" predicate (with nested property name) with "filter" then too working

g.V().hasLabel('object_model').as('m').has('s_model','abc.iaTest.some.engineering')
  .filter(__.values('p_models.abc_test_amxyz_assetCriticality.typeId')
          .is('AssetCriticalityTypeBModel'))  - **record getting returned**