J
JanusGraph•3mo ago
rpuga

Mapping.STRING not working as expected?

Hi everyone! Based on the Janusgraph text search documentation: 
When a string mapping is configured, the string value is indexed and can be queried "as-is" - including stop words and non-letter characters
When a string mapping is configured, the string value is indexed and can be queried "as-is" - including stop words and non-letter characters
However, this does not seem to work as expected. Example: I have an index that looks like this: 
ipstr = mgmt.makePropertyKey('ip_str').dataType(String.class).make()
mgmt.buildIndex('ipstrVMixedIndex', Vertex.class).addKey(ipstr, Mapping.STRING.asParameter()).buildMixedIndex("search")
ipstr = mgmt.makePropertyKey('ip_str').dataType(String.class).make()
mgmt.buildIndex('ipstrVMixedIndex', Vertex.class).addKey(ipstr, Mapping.STRING.asParameter()).buildMixedIndex("search")
and nodes of type ipaddr that have ip_str propery values like 192.168.1.0/24 as well as 10.24.2.3 (no CIDR). Now when I run a query like: 
g.V().has("ipaddr", "ip_str", textContains("/24"))
g.V().has("ipaddr", "ip_str", textContains("/24"))
it returns both IPs that end in /24 as well as IPs that happen to contain 24 in them, like the two examples above. This does not seem to match the expected behavior based on my understanding of the Mapping.STRING documentation. Am I missing something? Thanks! PS: the indexing backend is ES, in case it is important
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?