Connie,
The error was due to missing request header: -H 'Content-Type:
application/json'. Can you try the following?
curl -iv -H 'Content-Type: application/json' -u admin:admin -X POST
atlas-server/api/atlas/v2/search/basic -d '{
"excludeDeletedEntities": true,
"classification" : "PII",
"query" : "",
"limit" : 50,
"offset" : 0,
"entityFilters" : null,
"tagFilters" : {
"attributeName" : "pii_type",
"operator" : "eq",
"attributeValue": "example"
},
"attributes": [""]
}'
Hope this helps.
Madhan
From: Connie Chen <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Wednesday, December 6, 2017 at 11:38 AM
To: "[email protected]" <[email protected]>
Subject: Re: 500 returns when I try to basic search
I tried an example from the suggested queries applied to classification, like
`PII PII.type="name"` and got this error
2017-12-06 19:36:35,743 ERROR - [pool-1-thread-7 -
4cdc2d8b-f710-4c59-9eb2-ef7560801a74:] ~ Error handling a request:
e83408f35ae8fcd6 (ExceptionMapperUtil:32)
org.apache.atlas.exception.AtlasBaseException: Discovery query failed L:{def
r=(([]) as Set);def f1={GremlinPipeline
x->x.as('theTrait').in().as('theInstance') [0..<25].select(['theTrait',
'theInstance']).fill(r)};f1(g.V().has('__typeName','PII'));f1(g.V().has('__superTypeNames','PII'));r._().as('__tmp').transform({((Row)it).getColumn('theTrait')}).as('theTrait').back('__tmp').transform({((Row)it).getColumn('theInstance')}).as('theInstance').select(['theTrait',
'theInstance'],{[it]},{[it]}).as('a0').has('PII.type').back('a0')
[0..<25].toList()}
at
org.apache.atlas.discovery.EntityDiscoveryService.searchUsingDslQuery(EntityDiscoveryService.java:143)
at org.apache.atlas.web.rest.DiscoveryREST.searchUsingDSL(DiscoveryREST.java:94)
On Wed, Dec 6, 2017 at 11:30 AM, Connie Chen <[email protected]> wrote:
Hi Madhan, thanks for looking. I changed the config properties but getting the
same error. I don't see the "Given type" error in the startup anymore though:
https://gist.github.com/connie-stripe/597e087433869036e63e5d8363d61bd3#file-taxonomy-enable-false
I also tried an advanced search in the UI I think that was causing those
`Discovery query` errors. Let me know what you think, thanks
Connie
On Wed, Dec 6, 2017 at 11:00 AM, Madhan Neethiraj <[email protected]> wrote:
Connie,
The query text is correct; it works in my env. The log file shows failures in
bunch of other calls as well:
- com.sun.jersey.api.NotFoundException: null for uri:
http://atlas-server.service.consul:21000/api/atlas/discovery/search/basic
- com.sun.jersey.api.NotFoundException: null for uri:
http://atlas-server.service.consul:21000/api/atlas/v2/types/typedefs/classification
- com.sun.jersey.api.NotFoundException: null for uri:
http://atlas-server.service.consul:21000/api/atlas/v2/discovery/search/attribute?attrName=dataType
- org.apache.atlas.exception.AtlasBaseException: Discovery query failed
L:{def r=(([]) as Set);def f1={GremlinPipeline
x->x.as('theTrait').in().as('theInstance') [0..<25].select(['theTrait',
'theInstance']).fill(r)};f1(g.V().has('__typeName','PII'));f1(g.V().has('__superTypeNames','PII'));r._().as('__tmp').transform({((Row)it).getColumn('theTrait')}).as('theTrait').back('__tmp').transform({((Row)it).getColumn('theInstance')}).as('theInstance').select(['theTrait',
'theInstance'],{[it]},{[it]}).as('a0').has('PII.dataType',T.'eq','example').back('a0')
[0..<25].toList()}
- org.apache.atlas.exception.AtlasBaseException: Discovery query failed PII
OR Metric
- org.apache.atlas.exception.AtlasBaseException: Discovery query failed
Column WHERE Column isa PII
Log file shows a restart of Atlas running into the following error during
initialization: “Given type TaxonomyTerm already exists”. If taxonomy feature
(which is in tech-preview) is enabled, can you try after disabling it? Please
set the following configuration in atlas-application.properties:
atlas.feature.taxonomy.enable=false
Madhan
From: Nixon Rodrigues <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Wednesday, December 6, 2017 at 1:04 AM
To: "[email protected]" <[email protected]>
Subject: Re: 500 returns when I try to basic search
Connie,
Can you try this json as the body, I think to search on attribute needs to be
added to in criterion attribute.
http://atlasUrl:21000/api/atlas/v2/search/basic method - post
{
"excludeDeletedEntities": true,
"entityFilters": null,
"tagFilters": {
"criterion": [
{
"attributeName": "type",
"operator": "eq",
"attributeValue": "example"
}
]
},
"attributes": [],
"limit": 25,
"offset": 0,
"classification": "PII"
}
On Wed, Dec 6, 2017 at 11:50 AM, Connie Chen <[email protected]> wrote:
Hi Madhan, thanks for the fast response.
I added the snippet of the application log that shows the stack trace when I
make the search request.
https://gist.github.com/connie-stripe/597e087433869036e63e5d8363d61bd3#gistcomment-2277245
I also added as much of the application log as I could in another file
https://gist.github.com/connie-stripe/597e087433869036e63e5d8363d61bd3#file-application-log
Let me know if that helps, thanks!
Connie
On Tue, Dec 5, 2017 at 6:41 PM, Madhan Neethiraj <[email protected]> wrote:
Connie,
Thanks for the details provided on this issue. Classification definition and
basic-search REST API call details look good. To troubleshoot further, can you
add complete application.log file?
Madhan
From: Connie Chen <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Tuesday, December 5, 2017 at 5:17 PM
To: "[email protected]" <[email protected]>
Subject: 500 returns when I try to basic search
Hi, I am new to using Atlas and I am testing out the API to create my data
models. I've created a classification with a string attribute "dataType" where
"isIndexable" is set to true. However, I cannot figure out how to query for a
specific value via the API without getting a 500.
Here is my configuration:
https://gist.github.com/connie-stripe/597e087433869036e63e5d8363d61bd3
This is the field I am indexing on:
https://gist.github.com/connie-stripe/597e087433869036e63e5d8363d61bd3#file-gistfile1-txt-L22
Here is the curl command I am running to try and retrieve a value where that
attribute field is a specific value:
https://gist.github.com/connie-stripe/597e087433869036e63e5d8363d61bd3#gistcomment-2277045
Then I am getting these logs back:
https://gist.github.com/connie-stripe/597e087433869036e63e5d8363d61bd3#gistcomment-2277047
Am I doing something wrong? Is there an easier way to debug these sorts of
errors? The stack trace hasn't been very helpful. Thanks!
Connie
