atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <>
Subject [jira] [Commented] (ATLAS-263) Searching for a multi word trait always returns empty result
Date Wed, 09 Dec 2015 11:29:11 GMT


Suma Shivaprasad commented on ATLAS-263:

[~girishrp] I tested the above steps with the latest ATLAS build and the discovery query works
with the backtick ` like you mentioned.

curl -v http://localhost:21000/api/atlas/discovery/search?query=`multi%20word%20trait` 

{"requestId":"qtp1311760211-13 - e8ca55f3-0a63-4f01-973f-e6e7ed5b8069","query":"`multi word
word trait","multiplicity":{"lower":0,"upper":1,"isUnique":false},"isComposite":false,"isUnique":false,"isIndexable":true,"reverseAttributeName":null},{"name":"instanceInfo","dataTypeName":"__IdType","multiplicity":{"lower":0,"upper":1,"isUnique":false},"isComposite":false,"isUnique":false,"isIndexable":true,"reverseAttributeName":null}]}}

Can you please instead submit a patch for documentation example in Search.twiki and QuickStart
giving an example of this?

> Searching for a multi word trait always returns empty result
> ------------------------------------------------------------
>                 Key: ATLAS-263
>                 URL:
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.6-incubating
>            Reporter: Ayub Khan
>            Assignee: Girish Ramachandran
>            Priority: Blocker
>             Fix For: trunk
>         Attachments: types_query_fix.patch
> Searching for a multi word trait always returns empty result..
> 1. Create a trait name with multiple words..
> 	Example: 
> {noformat}
> curl 'http://localhost:21000/api/atlas/types' -H 'Origin: http://localhost:21000'  -H
'Content-Type: application/json;charset=UTF-8' --data-binary '{"enumTypes":[],"traitTypes":[{"superTypes":[],"typeName":"multi
word trait","attributeDefinitions":[],"hierarchicalMetaTypeName":"org.apache.atlas.typesystem.types.TraitType"}],"structTypes":[],"classTypes":[]}'
> {noformat}
> 2. Attach the tag with an entity
> 	Example:
> {noformat}
> curl -v 'http://localhost:21000/api/atlas/entity/803f5bdd-28f9-49e1-8c21-3dc0f9fd5c61/traits'
-H 'Content-Type: application/json;charset=UTF-8' --data-binary '{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct","typeName":"multi
word trait","values":{}}' --compressed
> {noformat}
> 3. Now try to get all the entities associated with the tag
> 	Example:
> {noformat}
> curl 'http://localhost:21000/api/atlas/discovery/search?query=multi+word+trait'
> {noformat}
> 	Result of the above is always empty because the above query is triggered as "full text"
and it always returns empty result even if you have associated entites to the tag.
> This is a big issue from an end user's perspective. marking this as a blocker

This message was sent by Atlassian JIRA

View raw message