[jira] [Updated] (ATLAS-996) DSL queries with comparsions of many primitive types fail

["Madhan Neethiraj (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ATLAS-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Madhan Neethiraj updated ATLAS-996:
-----------------------------------
    Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/36a6444218ee05853c052385ea066383877e9b5f

> DSL queries with comparsions of many primitive types fail
> ---------------------------------------------------------
>
>                 Key: ATLAS-996
>                 URL: https://issues.apache.org/jira/browse/ATLAS-996
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Jeffrey Hagelberg
>            Assignee: Jeffrey Hagelberg
>             Fix For: 0.8-incubating, 0.7.1-incubating
>
>         Attachments: ATLAS-996-final.patch, ATLAS-996-final.patch, org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest-output.txt, org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest.txt, rb49771.patch
>
>
> We have a test case we've added in our git fork that compares attributes with all of the various primitive types to literal values.  These are very simple quries such as "Person where (salary >= 200000)" for all of the different comparison operators and data types.  We just discovered that these tests were failing in the titan 0.5.4 implementation with a ClassCastException (for example, for double type, the literal was being interpreted in Gremlin as integer literal, and it could not cast it to a double to do the comparison) .  We have put in a fix for this issue in our fork.  This JIRA is to merge the test case as well as the code that fixes the issue into the Atlas master. 
> We also discovered that GraphBackedSearchIndexer.initialize() leaves the TitanManagement transaction open when it returns early because the global indices already exist.  That was fixed as well.



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