[jira] [Commented] (ATLAS-1346) Search APIs should return empty list instead of throwing exception

["Hemanth Yamijala (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711228#comment-15711228 ] 

Hemanth Yamijala commented on ATLAS-1346:
-----------------------------------------

A long while back, on ATLAS-805, we discovered that Titan's read only operations also could end up mutating some underlying indexes. Without proper transaction boundaries, this seemed to cause some failures for operations run after the read queries - please look at this comment in particular: https://issues.apache.org/jira/browse/ATLAS-805?focusedCommentId=15289274&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15289274

So, could you please double-check if removing transactionality is still OK?

> Search APIs should return empty list instead of throwing exception
> ------------------------------------------------------------------
>
>                 Key: ATLAS-1346
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1346
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.8-incubating
>            Reporter: Apoorv Naik
>            Assignee: Apoorv Naik
>             Fix For: 0.8-incubating
>
>
> Currently the APIs return a 404 when there's no result found in the repository which causes the graph transaction to rollback, instead the search API should return an empty list and the rest layer should translate it to a 404 or the read-only APIs should be excluded from the GraphTransaction interceptor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)