[ATLAS-2117] Basic search issues due to Titan Solr schema

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8-incubating, 0.8.1, 1.0.0
• Fix Version/s: 0.8.2, 1.0.0
• Assignee: Apoorv Naik
• Reporter: Apoorv Naik
• Created: 06/Sep/17 05:56
• Updated: 12/Apr/18 20:12
• Resolved: 12/Apr/18 20:12

Description

When using Solr as indexing backend, the tokenization of the string is performed using the StandardTokenizerFactory which treats punctuations and special characters as delimiters which results in the more indexed terms being associated with the associated vertex (document)

Also there's a LowercaseFilterFactory which makes lookup case insensitive.

This schema design doesn't work well for the current basic search enhancement (ATLAS-1880) causing a lot of false positives/negatives when querying the index.

The workaround/hack for this is to do an in-memory filtering when such schema violations are found or push the entire attribute query down to the graph which might be in-efficient and memory intensive. (Current JIRA will track this)

Correct solution would be to re-index the existing data with a schema change and not use the mentioned code workarounds for better performance of the search. (Should be taken up in separate JIRA)

Issue Links

• is duplicated by: ATLAS-2121 Inconsistency in basic search results due to case sensitivity of type names
• relates to: ATLAS-2091 Search using entity and trait attributes - "#" in string attribute filter doesn't fetch results
• links to: https://reviews.apache.org/r/62129/