https://github.com/apache/atlas/blob/master/repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java
This is where the query is getting formed, I don't recall where the double quotes are getting injected around the attribute value. Let me dig into this more but someone more active should be able to assist you in a better way. On Mon, Apr 22, 2019 at 9:18 AM Apoorv Naik <[email protected]> wrote: > AFAIK, the current implementation of the search is tuned for Solr. For > Elastic search, you'll have to make some adjustments. I think the query > provider logic is pluggable and configurable, so if you create a ES > specific provider and configure Atlas to use that, this problem can be > fixed. > > On Mon, Apr 22, 2019 at 8:55 AM Nallapati, Sreenivasulu < > [email protected]> wrote: > >> Hello Atlas team, >> >> >> >> Have observed when if there is a ['@','/',' ','-'] char in the attribute >> filter query (ex: table-) in Start with/Ends with/contains queries, the >> Elastic search query becomes >> >> Start with => "table-"* >> >> Ends with => *"table-" >> >> Contains => *"table-"* >> >> >> >> The question is, the * should be outside of double quotes ("table-"*) or >> with in double quotes ("table-*")? Elasticsearch is returning all the >> entitites in the system if * is outside of the double quotes and it takes >> very long times with offset and limit paginations. >> >> We are assuming the * should be with in double quotes. >> >> Please clarify, is this a expected behaviour or a bug >> >> >> >> It is very critical for our use case with special chars in the attribute >> filter search. >> >> >> >> >> >> --- >> >> Regards, >> >> Sreeni >> >
