[jira] [Commented] (ATLAS-4884) approximateCount confused
[
https://issues.apache.org/jira/browse/ATLAS-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863122#comment-17863122
]
Pinal Shah commented on ATLAS-4884:
---
[~zhangminguang]
# While using `__customAttribute` in basic search filter, approximateCount is
incorrect, it is a bug, i have created ticket ATLAS-4885, will fix in a day
# For your usecase regarding custom entity type and filtering it with its
attribute, it is possible to search through DSL. but filtering through
`__customAttributes`(UserDefined Attributes) is not supported in DSL
> approximateCount confused
> -
>
> Key: ATLAS-4884
> URL: https://issues.apache.org/jira/browse/ATLAS-4884
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: MinGuang Zhang
>Priority: Major
> Attachments: image-2024-06-26-11-58-18-440.png,
> image-2024-06-26-11-58-50-435.png
>
>
> atlas should return search result total exactly when user post some search
> Conditions, like query string and filter. Is using approximateCount as
> total? but approximateCount make me confused.
> a general scene： i want the total of search result for page i one request.
> but now i should recall api to add limit (eg: 10+) .
> the bad way: to reduce paramaters for get all and return hurge data for
> calculate.
>
> {*}Problem 1{*}:
> the response of post "/search/basic" api.
> see picture1 , i'm not add filter and set search text to find the hive_table
> contains my custom attributes, the approximateCount is correct。 by the way,
> is DSL support find __customAttribute?? how to do?
> picture 1:
> !image-2024-06-26-11-58-18-440.png!
>
> see picture2, i'm add filter and not set search text, the approximateCount
> is incorrect。 i see the correct total is 11 one by one.
> picture2
> !image-2024-06-26-11-58-50-435.png!
> also i can't using the entities size for work when the limit paramters
> changed.
> so how to search use defined attribute for work? use filter or fullText
> search? and is a bug? or need some total variable？
>
> {*}Problem 2{*}:
> Use-defined propertiies can help business . can support dsl search it ? any
> discuss will help me.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4885) Basic Search : not using index-search for Userdefined attributes
Pinal Shah created ATLAS-4885:
-
Summary: Basic Search : not using index-search for Userdefined
attributes
Key: ATLAS-4885
URL: https://issues.apache.org/jira/browse/ATLAS-4885
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
While searching through basic search having filter for userdefined attribute,
getting below warning log
{code:java}
not using index-search for attribute '__customAttributes'; might cause poor
performance (SearchProcessor:337)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4882:
--
Description:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*Steps to Repro:*
* Make sure backend has above 1M entities
* Start creating tables under `db1@cm`
* Start export for `db1@cm`
*
{code:java}
curl -v -X POST -u admin:admin -H "Content-Type: application/json"
"http://<>/api/atlas/admin/export" -d
'{"itemsToExport":[{"typeName":"hive_db","uniqueAttributes": { "qualifiedName":
"db1@cm" }}],"options":{"fetchType":"full","replicatedTo":"cm"}} >
export1.zip{code}
* It fails after sometime.
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465 {code}
- ran same query through gremlin shell while ingestion is happening it doesn't
fail
- time taken for above gremlin query in code when ingestion :
214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion
: 181682ms
Still Root cause is unknown
*WorkAround:*
- Remove .has('__guid') clause from below, it is very quick and issue is not
reproducible.
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
*Tests:*
* upgrded tinkerpop and janusgraph version but didn't help
* invalid property doesn't throw any exception or not existence of property
was:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=
[jira] [Updated] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4882:
--
Description:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465 {code}
- ran same query through gremlin shell while ingestion is happening it doesn't
fail
- time taken for above gremlin query in code when ingestion :
214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion
: 181682ms
Still Root cause is unknown
*WorkAround:*
- Remove .has('__guid') clause from below, it is very quick and issue is not
reproducible.
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
was:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&
[jira] [Updated] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4882:
--
Description:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465 {code}
- ran same query through gremlin shell while ingestion is happening it doesn't
fail
- time taken for above gremlin query in code when ingestion :
214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion
: 181682ms
Still Root cause is unknown
*WorkAround:*
- Remove .has('__guid') clause from below, it is very quick
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
was:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
g.V().has('__typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid')
- has('__guid') queries [(35x_t <> null)]:vertex_index , checked timetaken in
the solr logs
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=java
[jira] [Updated] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
[
https://issues.apache.org/jira/browse/ATLAS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4882:
--
Description:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465 {code}
- ran same query through gremlin shell while ingestion is happening it doesn't
fail
- time taken for above gremlin query in code when ingestion :
214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion
: 181682ms
Still Root cause is unknown
*WorkAround:*
- Remove .has('__guid') clause from below, it is very quick and issue is not
reproducible.
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid'){code}
*Tests:*
* upgrded tinkerpop and janusgraph version but didn't help
* invalid property doesn't throw any exception or not existence of property
was:
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
{code:java}
g.V().has('_typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('guid').values('_guid'){code}
- has('__guid') queries solr [(35x_t <> null)]:vertex_index
- below is the timetaken in the solr logs
{code:java}
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params={q=:&stateVer=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x
[jira] [Created] (ATLAS-4882) Export/Import: Export exits with "Found 0 entities"
Pinal Shah created ATLAS-4882:
-
Summary: Export/Import: Export exits with "Found 0 entities"
Key: ATLAS-4882
URL: https://issues.apache.org/jira/browse/ATLAS-4882
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
*Issue:*
Export during ingestion fails giving Found 0 entities in the logs
Ingestion meaning Atlas is consuming messages
*When is the issue seen?*
It occurs when there is huge amount of data in backend and Atlas is consuming
messages linked to entity of which export is running
*Analysis to find Root cause:*
* when there is huge amount of data in backend, export FAILS
* when there is huge amount of data in backend but less tables under it, then
also export FAILS
* if background consumption stops, export PASS
* if consumption is of different entities then requested in export, export PASS
* export query to find starting object uses below query, where has clause to
check property is expensive
g.V().has('__typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid')
- has('__guid') queries [(35x_t <> null)]:vertex_index , checked timetaken in
the solr logs
2024-06-14 02:38:56.218 INFO (qtp1158676965-19) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=0&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1681928 status=0 QTime=4227
2024-06-14 02:40:23.945 INFO (qtp1158676965-16) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=50&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682086 status=0 QTime=787
2024-06-14 02:41:37.703 INFO (qtp1158676965-14) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=100&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682216 status=0 QTime=1962
2024-06-14 02:42:20.715 INFO (qtp1158676965-20) [c:vertex_index s:shard1
r:core_node2 x:vertex_index_shard1_replica_n1] o.a.s.c.S.Request
[vertex_index_shard1_replica_n1] webapp=/solr path=/select
params=\{q=*:*&_stateVer_=vertex_index:12&fl=id&start=150&fq=35x_t:*+&rows=50&wt=javabin&version=2}
hits=1682363 status=0 QTime=4465
- ran same query through gremlin shell while ingestion is happening it doesnt
fail
- time taken for above gremlin query in code when ingestion : 214825ms
- time takem for above gremlin query in gremlin shell when ingestion : 104641ms
- time taken for above gremlin query when no ingestion : 181682ms
WorkAround
- Remove .has('__guid') clause from below, it is very quick
g.V().has('__typeName','hive_db').has('Referenceable.qualifiedName','db6@cm').has('__guid').values('__guid')
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4866) Export/Import: Skip adding processed guids in audit while importing huge zip
[
https://issues.apache.org/jira/browse/ATLAS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4866:
--
Description:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When large sized export zipped file is imported, import gives below error,
internally import gets succesful, but fail creating audit.
{code:java}
{"errorCode":"ATLAS-500-00-001","errorMessage":"org.janusgraph.core.JanusGraphException:
Could not commit transaction due to exception during
persistence","errorCause":"Could not commit transaction due to exception during
persistence"}
{code}
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
*Solution:*
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry when size of entity goes beyond the value stored in
bytes below
{code:java}
atlas.hbase.client.keyvalue.maxsize{code}
was:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When large sized export zipped file is imported, import gives below error,
internally import gets succesful, but fail creating audit.
_{"errorCode":"ATLAS-500-00-001","errorMessage":"org.janusgraph.core.JanusGraphException:
Could not commit transaction due to exception during
persistence","errorCause":"Could not commit transaction due to exception during
persistence"}_
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
[jira] [Updated] (ATLAS-4866) Export/Import: Skip adding processed guids in audit while importing huge zip
[
https://issues.apache.org/jira/browse/ATLAS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4866:
--
Description:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When large sized export zipped file is imported, import gives below error,
internally import gets succesful, but fail creating audit.
_{"errorCode":"ATLAS-500-00-001","errorMessage":"org.janusgraph.core.JanusGraphException:
Could not commit transaction due to exception during
persistence","errorCause":"Could not commit transaction due to exception during
persistence"}_
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
*Solution:*
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry when size of entity goes beyond the value stored in
bytes below
{code:java}
atlas.hbase.client.keyvalue.maxsize{code}
was:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.g
[jira] [Updated] (ATLAS-4866) Export/Import: Skip adding processed guids in audit while importing huge zip
[
https://issues.apache.org/jira/browse/ATLAS-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4866:
--
Description:
*Background:*
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
*Issue:*
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
*Solution:*
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry when size of entity goes beyond the value stored in
bytes below
{code:java}
atlas.hbase.client.keyvalue.maxsize{code}
was:
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry
> Export/Import: Skip a
[jira] [Created] (ATLAS-4866) Export/Import: Skip adding processed guids in audit while importing huge zip
Pinal Shah created ATLAS-4866:
-
Summary: Export/Import: Skip adding processed guids in audit while
importing huge zip
Key: ATLAS-4866
URL: https://issues.apache.org/jira/browse/ATLAS-4866
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
Atlas uses HBase as its store for audit repository.
After import, atlas store the audit entity with the import information along
with all the processed entitiy guids.
When size of the entity is greater than "hbase.client.keyvalue.maxsize"
property then audit entity creation fails with exception.
{code:java}
Caused by: org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException:
Failed 1 action: org.apache.hadoop.hbase.DoNotRetryIOException:
Cell[\x00\x00\x00\x00\x00\x00\x00\x00\x01\x05\xCC\xBB/l:\x00\x06\x18r\xB0\xBE\xFDH\xA00a11ed186467-ve0214-halxg-cloudera-com\xB2\x00\x00\x00\x00\x00\x0D\xB6Y/1715730740890001/Put/vlen=23826488/seqid=0]
with size 23826581 exceeds limit of 10485760 bytes
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.checkCellSizeLimit(RSRpcServices.java:906)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doBatchOp(RSRpcServices.java:992)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicBatchOp(RSRpcServices.java:927)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:892)
at
org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2855)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45961)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:387)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:139)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:369)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:349)
: 1 time, servers with issues: ve0214.halxg.cloudera.com,22101,1715690875185
at
org.apache.hadoop.hbase.client.BatchErrors.makeException(BatchErrors.java:50)
at
org.apache.hadoop.hbase.client.AsyncRequestFutureImpl.getErrors(AsyncRequestFutureImpl.java:1228)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:434)
at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:422)
at org.janusgraph.diskstorage.hbase2.HTable2_0.batch(HTable2_0.java:51)
{code}
Hence in this case, storing processed entities guids is skipped while creating
ExportImportAuditEntry
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4865) Documentation: Add features, improvement which are missing in the doc
Pinal Shah created ATLAS-4865: - Summary: Documentation: Add features, improvement which are missing in the doc Key: ATLAS-4865 URL: https://issues.apache.org/jira/browse/ATLAS-4865 Project: Atlas Issue Type: Task Components: atlas-webui Affects Versions: 2.3.0 Reporter: Pinal Shah Assignee: Pinal Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4864) BasicSearch: Search with combination of terms and freetext, works incorrectly
Pinal Shah created ATLAS-4864: - Summary: BasicSearch: Search with combination of terms and freetext, works incorrectly Key: ATLAS-4864 URL: https://issues.apache.org/jira/browse/ATLAS-4864 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah Attachments: Screen Shot 2020-06-08 at 4.03.35 PM (1).png Filter of freetext query doen't apply on the term result. !Screen Shot 2020-06-08 at 4.03.35 PM (1).png|width=744,height=303! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4863) NPE while deleting BusinessMetadata
Pinal Shah created ATLAS-4863:
-
Summary: NPE while deleting BusinessMetadata
Key: ATLAS-4863
URL: https://issues.apache.org/jira/browse/ATLAS-4863
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
If businessMetadata is created without adding any applicable types, we get
NullPointerException when we try to delete that businessmetadata.
Example:
{code:java}
{
"category": "BUSINESS_METADATA",
"guid": "678dc8e1-3897-4b43-94f2-929ea984e8d9",
"createdBy": "h0650206",
"updatedBy": "h0650206",
"createTime": 1714471319783,
"updateTime": 1714731363238,
"version": 3,
"name": "test_create_bussiness_metadata",
"description": "test_create_bussiness_metadata",
"typeVersion": "1.1",
"attributeDefs": [
{
"name": "test",
"typeName": "string",
"isOptional": true,
"cardinality": "SINGLE",
"valuesMinCount": 0,
"valuesMaxCount": 1,
"isUnique": false,
"isIndexable": true,
"includeInNotification": false,
"searchWeight": 0,
"options": {
"applicableEntityTypes": "[]",
"maxStrLength": "50"
}
}
]
} {code}
If above businessMetadata type is deleted, we get below exception
{code:java}
java.lang.NullPointerException
at java.base/java.util.Objects.requireNonNull(Objects.java:221)
at java.base/java.lang.String.join(String.java:2440)
at
org.apache.atlas.repository.store.graph.v2.AtlasBusinessMetadataDefStoreV2.isBusinessAttributePresent(AtlasBusinessMetadataDefStoreV2.java:425)
at
org.apache.atlas.repository.store.graph.v2.AtlasBusinessMetadataDefStoreV2.checkBusinessMetadataRef(AtlasBusinessMetadataDefStoreV2.java:408)
at
org.apache.atlas.repository.store.graph.v2.AtlasBusinessMetadataDefStoreV2.preDeleteByGuid(AtlasBusinessMetadataDefStoreV2.java:342)
at
org.apache.atlas.repository.store.graph.v2.AtlasAbstractDefStoreV2.deleteByGuid(AtlasAbstractDefStoreV2.java:153)
at
org.apache.atlas.repository.store.graph.v2.AtlasBusinessMetadataDefStoreV2.deleteByGuid(AtlasBusinessMetadataDefStoreV2.java:55)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.deleteTypesDef(AtlasTypeDefGraphStore.java:669)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore.deleteTypeByName(AtlasTypeDefGraphStore.java:714)
at
org.apache.atlas.repository.store.graph.AtlasTypeDefGraphStore$$FastClassBySpringCGLIB$$5226c80b.invoke()
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4861) Export/Import: add flag to skip updating replicated attributes
Pinal Shah created ATLAS-4861: - Summary: Export/Import: add flag to skip updating replicated attributes Key: ATLAS-4861 URL: https://issues.apache.org/jira/browse/ATLAS-4861 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah *Replicated Attributes:* Users want knowledge of how the entities have landed into Atlas instance, if they were created via hook ingestion or whether they were imported from another Atlas instance. This is addressed by 2 new attributes that are now part of _Referenceable_ entity type viz. _replicatedFrom_ and _replicatedTo_. *Current Behaviour:* At the end of export/import, the entities which are exported/imported are updated with the replicationTo/replicationFrom respectively with the value of AtlasServer object Hence updating each and every entity takes much time. *Improvement:* Add flag to skip such updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4807) Fix IT test related to Labels
[ https://issues.apache.org/jira/browse/ATLAS-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah resolved ATLAS-4807. --- Resolution: Fixed > Fix IT test related to Labels > - > > Key: ATLAS-4807 > URL: https://issues.apache.org/jira/browse/ATLAS-4807 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > testSetLabelsByTypeName(org.apache.atlas.web.integration.EntityV2JerseyResourceIT) > test is failing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4807) Fix IT test related to Labels
[ https://issues.apache.org/jira/browse/ATLAS-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4807: -- Fix Version/s: 3.0.0 2.3.0 > Fix IT test related to Labels > - > > Key: ATLAS-4807 > URL: https://issues.apache.org/jira/browse/ATLAS-4807 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > testSetLabelsByTypeName(org.apache.atlas.web.integration.EntityV2JerseyResourceIT) > test is failing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4807) Fix IT test related to Labels
Pinal Shah created ATLAS-4807: - Summary: Fix IT test related to Labels Key: ATLAS-4807 URL: https://issues.apache.org/jira/browse/ATLAS-4807 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah testSetLabelsByTypeName(org.apache.atlas.web.integration.EntityV2JerseyResourceIT) test is failing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4796) Support Opensearch
Pinal Shah created ATLAS-4796: - Summary: Support Opensearch Key: ATLAS-4796 URL: https://issues.apache.org/jira/browse/ATLAS-4796 Project: Atlas Issue Type: New Feature Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah Adding support to opensearch will help users in place of Elasticsearch. But, janusgraph doesn't have support for opensearch as the indexing backend. Hence supporting it, by adding janusgraph elasticsearch dependency and opensearch rest client dependency -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4778) BusinessMetadata string attribute value persists as prefix and suffix
Pinal Shah created ATLAS-4778: - Summary: BusinessMetadata string attribute value persists as prefix and suffix Key: ATLAS-4778 URL: https://issues.apache.org/jira/browse/ATLAS-4778 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Pinal Shah -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4776) Basic Search : not null userDefined Attributes return incorrect results
Pinal Shah created ATLAS-4776:
-
Summary: Basic Search : not null userDefined Attributes return
incorrect results
Key: ATLAS-4776
URL: https://issues.apache.org/jira/browse/ATLAS-4776
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
{*}Issue{*}: using not null operator with userDefined attributes, returns some
entities which doesn't have userDefined attirbutes.
{*}Reproduce{*}: Assign one userDefined attribute to X entity, Remove all the
userDefined attribute assigned to X entity. Search with notNull userDefined
attributes. Actual: Lists X entity
Expected: shouldn't list X entity, as all the attributes are removed.
{*}Cause{*}: As the userDefined attributes are stored in json format, when we
remove all the attributes, it removes all the list but it leaves *'{}'* blank
json, which matches the nonNull field.
{*}Fix{*}: While removing the userDefined, check the Empty list, and remove the
json object.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (ATLAS-4762) Basic search with classification as notNull/isNull returns wrong entities
[ https://issues.apache.org/jira/browse/ATLAS-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah reassigned ATLAS-4762: - Assignee: Pinal Shah > Basic search with classification as notNull/isNull returns wrong entities > - > > Key: ATLAS-4762 > URL: https://issues.apache.org/jira/browse/ATLAS-4762 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Abhishek Pal >Assignee: Pinal Shah >Priority: Major > > When searching for entities using basic search and filtering by entities > where classification is not null we get entities which are not having any > classification. > This is also true for the case where we are searching for entities with null > classifications > and when using quick search as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4727) admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is not indexed in the targeted index [vertex_index]'
[
https://issues.apache.org/jira/browse/ATLAS-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4727:
--
Fix Version/s: 3.0.0
> admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is
> not indexed in the targeted index [vertex_index]'
> -
>
> Key: ATLAS-4727
> URL: https://issues.apache.org/jira/browse/ATLAS-4727
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
>
> Issue:
> admin/audits , admin/purge calls throw 500 internal server error.
> Error:
> {code:java}
> java.lang.IllegalArgumentException: The used key
> [__AtlasAuditEntry.startTime] is not indexed in the targeted index
> [vertex_index] at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:435)
> at
> org.janusgraph.graphdb.database.IndexSerializer.getOrders(IndexSerializer.java:711)
> at
> org.janusgraph.graphdb.database.IndexSerializer.executeQuery(IndexSerializer.java:726){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4727) admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is not indexed in the targeted index [vertex_index]'
[
https://issues.apache.org/jira/browse/ATLAS-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4727:
--
Fix Version/s: 2.4.0
> admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is
> not indexed in the targeted index [vertex_index]'
> -
>
> Key: ATLAS-4727
> URL: https://issues.apache.org/jira/browse/ATLAS-4727
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
> Fix For: 2.4.0
>
>
> Issue:
> admin/audits , admin/purge calls throw 500 internal server error.
> Error:
> {code:java}
> java.lang.IllegalArgumentException: The used key
> [__AtlasAuditEntry.startTime] is not indexed in the targeted index
> [vertex_index] at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:435)
> at
> org.janusgraph.graphdb.database.IndexSerializer.getOrders(IndexSerializer.java:711)
> at
> org.janusgraph.graphdb.database.IndexSerializer.executeQuery(IndexSerializer.java:726){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4727) admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is not indexed in the targeted index [vertex_index]'
Pinal Shah created ATLAS-4727:
-
Summary: admin/audits , admin/purge APIs fail with
'[__AtlasAuditEntry.startTime] is not indexed in the targeted index
[vertex_index]'
Key: ATLAS-4727
URL: https://issues.apache.org/jira/browse/ATLAS-4727
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
Issue:
admin/audits , admin/purge calls throw 500 internal server error.
Error:
{code:java}
java.lang.IllegalArgumentException: The used key [__AtlasAuditEntry.startTime]
is not indexed in the targeted index [vertex_index] at
com.google.common.base.Preconditions.checkArgument(Preconditions.java:435)
at
org.janusgraph.graphdb.database.IndexSerializer.getOrders(IndexSerializer.java:711)
at
org.janusgraph.graphdb.database.IndexSerializer.executeQuery(IndexSerializer.java:726){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4681) Relationship Search : SortBy is not working
[ https://issues.apache.org/jira/browse/ATLAS-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4681: -- Fix Version/s: 3.0.0 2.3.0 > Relationship Search : SortBy is not working > --- > > Key: ATLAS-4681 > URL: https://issues.apache.org/jira/browse/ATLAS-4681 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > Currently Relationship Search supports filtering results. There is a sortBy > and sortOrder param that is supposed to sort according to the arguments > provided. > However currently it is return a random order of results even though the > filter is applied. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4681) Relationship Search : SortBy is not working
[ https://issues.apache.org/jira/browse/ATLAS-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4681: -- Component/s: atlas-core > Relationship Search : SortBy is not working > --- > > Key: ATLAS-4681 > URL: https://issues.apache.org/jira/browse/ATLAS-4681 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > Currently Relationship Search supports filtering results. There is a sortBy > and sortOrder param that is supposed to sort according to the arguments > provided. > However currently it is return a random order of results even though the > filter is applied. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4689) UI: Basic Search: Invalid attributes passed in request
Pinal Shah created ATLAS-4689: - Summary: UI: Basic Search: Invalid attributes passed in request Key: ATLAS-4689 URL: https://issues.apache.org/jira/browse/ATLAS-4689 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Pinal Shah Steps to Reproduce: Basic Search: # Search with typeName hive_db, attribute filter clusterName. # Search with typeName hive_table The request sent will have the 'clusterName' in 'attributes' field. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4685) Advanced Search : Not Equals operator doesn't work for String type
[ https://issues.apache.org/jira/browse/ATLAS-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4685: -- Fix Version/s: 3.0.0 2.3.0 > Advanced Search : Not Equals operator doesn't work for String type > -- > > Key: ATLAS-4685 > URL: https://issues.apache.org/jira/browse/ATLAS-4685 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > from hive_table where name != 'authors' select name, owner > If use the "!=" operator in where clause, it is not working as expected and > it still returns the row which has the value 'authors' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4531) _ALL_ENTITY_TYPES showing same basic search results even when offset is changed
[ https://issues.apache.org/jira/browse/ATLAS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4531: -- Component/s: atlas-core > _ALL_ENTITY_TYPES showing same basic search results even when offset is > changed > --- > > Key: ATLAS-4531 > URL: https://issues.apache.org/jira/browse/ATLAS-4531 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Rahul Kurup >Assignee: Pinal Shah >Priority: Minor > Fix For: 3.0.0, 2.3.0 > > > Whenever we fire a basic search for _ALL_ENTITY_TYPES, the same set of > results are always fetched even if you change the offset. > For ex: > If these are the results when you select page limit as 2 and offset as 0 > (there are total 59 results): > x1 > x2 > Then on increasing the offset to 3 you still get the above results x1 and x2. > This only occurs for _ALL_ENTITY_TYPES. If you search for specific data types > like hive_table and others the behaviour is normal. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4671) Basic Search : Exclude Header attributes of entities from the response
[ https://issues.apache.org/jira/browse/ATLAS-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4671: -- Fix Version/s: 3.0.0 > Basic Search : Exclude Header attributes of entities from the response > -- > > Key: ATLAS-4671 > URL: https://issues.apache.org/jira/browse/ATLAS-4671 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Labels: BasicSearch > Fix For: 3.0.0, 2.3.0 > > > *Issue* : Basic search has AtlasEntityHeader of each entity in the response. > AtlasEntityHeader has many attributes including classification and terms. > hence for each attribute, it will request janusgraph to get all the header > attributes. > *Approach* : To overcome, we can add a flag to exclude other attributes and > add only selected attributes from 'attributes' field in the response -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4531) _ALL_ENTITY_TYPES showing same basic search results even when offset is changed
[ https://issues.apache.org/jira/browse/ATLAS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4531: -- Fix Version/s: 3.0.0 2.3.0 > _ALL_ENTITY_TYPES showing same basic search results even when offset is > changed > --- > > Key: ATLAS-4531 > URL: https://issues.apache.org/jira/browse/ATLAS-4531 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Pinal Shah >Priority: Minor > Fix For: 3.0.0, 2.3.0 > > > Whenever we fire a basic search for _ALL_ENTITY_TYPES, the same set of > results are always fetched even if you change the offset. > For ex: > If these are the results when you select page limit as 2 and offset as 0 > (there are total 59 results): > x1 > x2 > Then on increasing the offset to 3 you still get the above results x1 and x2. > This only occurs for _ALL_ENTITY_TYPES. If you search for specific data types > like hive_table and others the behaviour is normal. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4685) Advanced Search : Not Equals operator doesn't work for String type
Pinal Shah created ATLAS-4685: - Summary: Advanced Search : Not Equals operator doesn't work for String type Key: ATLAS-4685 URL: https://issues.apache.org/jira/browse/ATLAS-4685 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah from hive_table where name != 'authors' select name, owner If use the "!=" operator in where clause, it is not working as expected and it still returns the row which has the value 'authors' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4681) Relationship Search : SortBy is not working
Pinal Shah created ATLAS-4681: - Summary: Relationship Search : SortBy is not working Key: ATLAS-4681 URL: https://issues.apache.org/jira/browse/ATLAS-4681 Project: Atlas Issue Type: Bug Reporter: Pinal Shah Assignee: Pinal Shah Currently Relationship Search supports filtering results. There is a sortBy and sortOrder param that is supposed to sort according to the arguments provided. However currently it is return a random order of results even though the filter is applied. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4531) _ALL_ENTITY_TYPES showing same basic search results even when offset is changed
[ https://issues.apache.org/jira/browse/ATLAS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah resolved ATLAS-4531. --- Resolution: Fixed > _ALL_ENTITY_TYPES showing same basic search results even when offset is > changed > --- > > Key: ATLAS-4531 > URL: https://issues.apache.org/jira/browse/ATLAS-4531 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Pinal Shah >Priority: Minor > > Whenever we fire a basic search for _ALL_ENTITY_TYPES, the same set of > results are always fetched even if you change the offset. > For ex: > If these are the results when you select page limit as 2 and offset as 0 > (there are total 59 results): > x1 > x2 > Then on increasing the offset to 3 you still get the above results x1 and x2. > This only occurs for _ALL_ENTITY_TYPES. If you search for specific data types > like hive_table and others the behaviour is normal. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4531) _ALL_ENTITY_TYPES showing same basic search results even when offset is changed
[ https://issues.apache.org/jira/browse/ATLAS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607499#comment-17607499 ] Pinal Shah commented on ATLAS-4531: --- Review board : https://reviews.apache.org/r/74017/ > _ALL_ENTITY_TYPES showing same basic search results even when offset is > changed > --- > > Key: ATLAS-4531 > URL: https://issues.apache.org/jira/browse/ATLAS-4531 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Pinal Shah >Priority: Minor > > Whenever we fire a basic search for _ALL_ENTITY_TYPES, the same set of > results are always fetched even if you change the offset. > For ex: > If these are the results when you select page limit as 2 and offset as 0 > (there are total 59 results): > x1 > x2 > Then on increasing the offset to 3 you still get the above results x1 and x2. > This only occurs for _ALL_ENTITY_TYPES. If you search for specific data types > like hive_table and others the behaviour is normal. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4671) Basic Search : Exclude Header attributes of entities from the response
Pinal Shah created ATLAS-4671: - Summary: Basic Search : Exclude Header attributes of entities from the response Key: ATLAS-4671 URL: https://issues.apache.org/jira/browse/ATLAS-4671 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah *Issue* : Basic search has AtlasEntityHeader of each entity in the response. AtlasEntityHeader has many attributes including classification and terms. hence for each attribute, it will request janusgraph to get all the header attributes. *Approach* : To overcome, we can add a flag to exclude other attributes and add only selected attributes from 'attributes' field in the response -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4671) Basic Search : Exclude Header attributes of entities from the response
[ https://issues.apache.org/jira/browse/ATLAS-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4671: -- Labels: BasicSearch (was: ) > Basic Search : Exclude Header attributes of entities from the response > -- > > Key: ATLAS-4671 > URL: https://issues.apache.org/jira/browse/ATLAS-4671 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Labels: BasicSearch > > *Issue* : Basic search has AtlasEntityHeader of each entity in the response. > AtlasEntityHeader has many attributes including classification and terms. > hence for each attribute, it will request janusgraph to get all the header > attributes. > *Approach* : To overcome, we can add a flag to exclude other attributes and > add only selected attributes from 'attributes' field in the response -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4619) Refactor Atlas webapp module to remove Kafka core dependency
[ https://issues.apache.org/jira/browse/ATLAS-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17580289#comment-17580289 ] Pinal Shah commented on ATLAS-4619: --- Precommit : https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1186 > Refactor Atlas webapp module to remove Kafka core dependency > > > Key: ATLAS-4619 > URL: https://issues.apache.org/jira/browse/ATLAS-4619 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Patrik Márton >Assignee: Patrik Márton >Priority: Major > > Goal is to break the strong coupling between Atlas components and Kafka. > These dependencies include using server side libraries of Kafka (this couples > the Scala version and other non-public interfaces of Kafka). Any code using > server side libraries of Kafka should be refactored. > Since atlas webapp module uses the ShutdownableThread from core kafka, it > should be refactored in a way to eliminate this dependency. > https://github.com/apache/atlas/blob/master/webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java#L526 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4569) Import kafka is failing with NoSuchMethod error
[
https://issues.apache.org/jira/browse/ATLAS-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah resolved ATLAS-4569.
---
Resolution: Fixed
> Import kafka is failing with NoSuchMethod error
> ---
>
> Key: ATLAS-4569
> URL: https://issues.apache.org/jira/browse/ATLAS-4569
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Disha Talreja
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Unable to perform kafka import as it is failing with the following exception.
> Log from console
> {code:java}
> > /opt/cloudera/parcels/CDH/lib/atlas
> Using Kafka configuration directory [/etc/kafka/conf]
> Log file for import is /var/log/atlas/import-kafka.log
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.23291269/jars/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.23291269/jars/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.log4j.helpers.OptionConverter.convertLevel(Ljava/lang/String;Lorg/apache/logging/log4j/Level;)Lorg/apache/logging/log4j/Level;
> at
> org.apache.log4j.xml.XmlConfiguration.parseLevel(XmlConfiguration.java:646)
> at
> org.apache.log4j.xml.XmlConfiguration.lambda$parseChildrenOfLoggerElement$4(XmlConfiguration.java:563)
> at
> org.apache.log4j.xml.XmlConfiguration.forEachElement(XmlConfiguration.java:762)
> at
> org.apache.log4j.xml.XmlConfiguration.parseChildrenOfLoggerElement(XmlConfiguration.java:548)
> at
> org.apache.log4j.xml.XmlConfiguration.parseCategory(XmlConfiguration.java:530)
> at
> org.apache.log4j.xml.XmlConfiguration.lambda$parse$6(XmlConfiguration.java:721)
> at
> org.apache.log4j.xml.XmlConfiguration.forEachElement(XmlConfiguration.java:762)
> at org.apache.log4j.xml.XmlConfiguration.parse(XmlConfiguration.java:717)
> at
> org.apache.log4j.xml.XmlConfiguration.doConfigure(XmlConfiguration.java:166)
> at
> org.apache.log4j.xml.XmlConfiguration.doConfigure(XmlConfiguration.java:141)
> at
> org.apache.log4j.config.Log4j1Configuration.initialize(Log4j1Configuration.java:60)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:293)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:626)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:699)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:716)
> at
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:270)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
> at
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:137)
> at
> org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:55)
> at
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:47)
> at
> org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:33)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:363)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:388)
> at org.apache.atlas.kafka.bridge.KafkaBridge.(KafkaBridge.java:56)
> Failed to import Kafka Data Model!!! {code}
> Issue is seen on 7.1.8 build: *23291269*
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (ATLAS-4569) Import kafka is failing with NoSuchMethod error
[
https://issues.apache.org/jira/browse/ATLAS-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4569:
--
Fix Version/s: 3.0.0
2.3.0
> Import kafka is failing with NoSuchMethod error
> ---
>
> Key: ATLAS-4569
> URL: https://issues.apache.org/jira/browse/ATLAS-4569
> Project: Atlas
> Issue Type: Bug
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Disha Talreja
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Unable to perform kafka import as it is failing with the following exception.
> Log from console
> {code:java}
> > /opt/cloudera/parcels/CDH/lib/atlas
> Using Kafka configuration directory [/etc/kafka/conf]
> Log file for import is /var/log/atlas/import-kafka.log
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.23291269/jars/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.23291269/jars/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.log4j.helpers.OptionConverter.convertLevel(Ljava/lang/String;Lorg/apache/logging/log4j/Level;)Lorg/apache/logging/log4j/Level;
> at
> org.apache.log4j.xml.XmlConfiguration.parseLevel(XmlConfiguration.java:646)
> at
> org.apache.log4j.xml.XmlConfiguration.lambda$parseChildrenOfLoggerElement$4(XmlConfiguration.java:563)
> at
> org.apache.log4j.xml.XmlConfiguration.forEachElement(XmlConfiguration.java:762)
> at
> org.apache.log4j.xml.XmlConfiguration.parseChildrenOfLoggerElement(XmlConfiguration.java:548)
> at
> org.apache.log4j.xml.XmlConfiguration.parseCategory(XmlConfiguration.java:530)
> at
> org.apache.log4j.xml.XmlConfiguration.lambda$parse$6(XmlConfiguration.java:721)
> at
> org.apache.log4j.xml.XmlConfiguration.forEachElement(XmlConfiguration.java:762)
> at org.apache.log4j.xml.XmlConfiguration.parse(XmlConfiguration.java:717)
> at
> org.apache.log4j.xml.XmlConfiguration.doConfigure(XmlConfiguration.java:166)
> at
> org.apache.log4j.xml.XmlConfiguration.doConfigure(XmlConfiguration.java:141)
> at
> org.apache.log4j.config.Log4j1Configuration.initialize(Log4j1Configuration.java:60)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:293)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:626)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:699)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:716)
> at
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:270)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
> at
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:137)
> at
> org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:55)
> at
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:47)
> at
> org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:33)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:363)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:388)
> at org.apache.atlas.kafka.bridge.KafkaBridge.(KafkaBridge.java:56)
> Failed to import Kafka Data Model!!! {code}
> Issue is seen on 7.1.8 build: *23291269*
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (ATLAS-4557) Dsl search with non-primitive attribute
[
https://issues.apache.org/jira/browse/ATLAS-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah reassigned ATLAS-4557:
-
Assignee: Pinal Shah
> Dsl search with non-primitive attribute
> ---
>
> Key: ATLAS-4557
> URL: https://issues.apache.org/jira/browse/ATLAS-4557
> Project: Atlas
> Issue Type: Wish
> Components: atlas-webui
>Affects Versions: 2.2.0
>Reporter: Hatice Ekenek
>Assignee: Pinal Shah
>Priority: Critical
>
> Hi,
> I have the following types.
> I want to list the contacts by filtering them according to the organization
> property. But I can't find the right method to do this. I would be glad if
> you help.
> dsl query example:
> Contact where organization.__guid = "d44532ea-c6fc-417b-8c59-f988777dd51f"
>
> Example entity types:
> Contact Entity:
> {
> "name": "Contact",
> "description": "Contact test. ",
> "superTypes": [
> "Referenceable"
> ],
> "serviceType": "workflow",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "isUnique": false
> },
> {
> "name": "organization",
> "typeName": "Organization",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "role",
> "typeName": "Role",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": true,
> "isUnique": false
> }
> ]
> }
>
> Organization Entity Type:
>
> {
> "name": "Organization",
> "description": "organization ",
> "superTypes": [
> "Referenceable"
> ],
> "serviceType": "workflow",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "organizationCode",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "organizationName",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": false,
> "isUnique": false
> }
> ]
> }
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (ATLAS-4557) Dsl search with non-primitive attribute
[
https://issues.apache.org/jira/browse/ATLAS-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah resolved ATLAS-4557.
---
Resolution: Fixed
> Dsl search with non-primitive attribute
> ---
>
> Key: ATLAS-4557
> URL: https://issues.apache.org/jira/browse/ATLAS-4557
> Project: Atlas
> Issue Type: Wish
> Components: atlas-webui
>Affects Versions: 2.2.0
>Reporter: Hatice Ekenek
>Assignee: Pinal Shah
>Priority: Critical
>
> Hi,
> I have the following types.
> I want to list the contacts by filtering them according to the organization
> property. But I can't find the right method to do this. I would be glad if
> you help.
> dsl query example:
> Contact where organization.__guid = "d44532ea-c6fc-417b-8c59-f988777dd51f"
>
> Example entity types:
> Contact Entity:
> {
> "name": "Contact",
> "description": "Contact test. ",
> "superTypes": [
> "Referenceable"
> ],
> "serviceType": "workflow",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "isUnique": false
> },
> {
> "name": "organization",
> "typeName": "Organization",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "role",
> "typeName": "Role",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": true,
> "isUnique": false
> }
> ]
> }
>
> Organization Entity Type:
>
> {
> "name": "Organization",
> "description": "organization ",
> "superTypes": [
> "Referenceable"
> ],
> "serviceType": "workflow",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "organizationCode",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "organizationName",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": false,
> "isUnique": false
> }
> ]
> }
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ATLAS-4557) Dsl search with non-primitive attribute
[
https://issues.apache.org/jira/browse/ATLAS-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498011#comment-17498011
]
Pinal Shah commented on ATLAS-4557:
---
Also, then you can fire dsl query like
{code:java}
Contact where organization.organizationName = 'ssbi' {code}
> Dsl search with non-primitive attribute
> ---
>
> Key: ATLAS-4557
> URL: https://issues.apache.org/jira/browse/ATLAS-4557
> Project: Atlas
> Issue Type: Wish
> Components: atlas-webui
>Affects Versions: 2.2.0
>Reporter: Hatice Ekenek
>Priority: Critical
>
> Hi,
> I have the following types.
> I want to list the contacts by filtering them according to the organization
> property. But I can't find the right method to do this. I would be glad if
> you help.
> dsl query example:
> Contact where organization.__guid = "d44532ea-c6fc-417b-8c59-f988777dd51f"
>
> Example entity types:
> Contact Entity:
> {
> "name": "Contact",
> "description": "Contact test. ",
> "superTypes": [
> "Referenceable"
> ],
> "serviceType": "workflow",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "isUnique": false
> },
> {
> "name": "organization",
> "typeName": "Organization",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "role",
> "typeName": "Role",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": true,
> "isUnique": false
> }
> ]
> }
>
> Organization Entity Type:
>
> {
> "name": "Organization",
> "description": "organization ",
> "superTypes": [
> "Referenceable"
> ],
> "serviceType": "workflow",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "organizationCode",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "organizationName",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": false,
> "isUnique": false
> }
> ]
> }
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (ATLAS-4557) Dsl search with non-primitive attribute
[
https://issues.apache.org/jira/browse/ATLAS-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498011#comment-17498011
]
Pinal Shah edited comment on ATLAS-4557 at 2/25/22, 9:41 AM:
-
Also, then you can fire dsl query like
{code:java}
Contact where organization.__guid = '99fc5750-a772-4b2d-ad40-9e00516cf644'
{code}
or
{code:java}
Contact where organization.organizationName = 'ssbi' {code}
was (Author: pinal.shah):
Also, then you can fire dsl query like
{code:java}
Contact where organization.organizationName = 'ssbi' {code}
> Dsl search with non-primitive attribute
> ---
>
> Key: ATLAS-4557
> URL: https://issues.apache.org/jira/browse/ATLAS-4557
> Project: Atlas
> Issue Type: Wish
> Components: atlas-webui
>Affects Versions: 2.2.0
>Reporter: Hatice Ekenek
>Priority: Critical
>
> Hi,
> I have the following types.
> I want to list the contacts by filtering them according to the organization
> property. But I can't find the right method to do this. I would be glad if
> you help.
> dsl query example:
> Contact where organization.__guid = "d44532ea-c6fc-417b-8c59-f988777dd51f"
>
> Example entity types:
> Contact Entity:
> {
> "name": "Contact",
> "description": "Contact test. ",
> "superTypes": [
> "Referenceable"
> ],
> "serviceType": "workflow",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "isUnique": false
> },
> {
> "name": "organization",
> "typeName": "Organization",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "role",
> "typeName": "Role",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": true,
> "isUnique": false
> }
> ]
> }
>
> Organization Entity Type:
>
> {
> "name": "Organization",
> "description": "organization ",
> "superTypes": [
> "Referenceable"
> ],
> "serviceType": "workflow",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "organizationCode",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "organizationName",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": false,
> "isUnique": false
> }
> ]
> }
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (ATLAS-4557) Dsl search with non-primitive attribute
[
https://issues.apache.org/jira/browse/ATLAS-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498010#comment-17498010
]
Pinal Shah commented on ATLAS-4557:
---
Please use below typeDef for your usecase.
{code:java}
{
"enumDefs": [{
"name": "Role",
"elementDefs": [{
"ordinal": 1,
"value": "ROLE1"
},
{
"ordinal": 2,
"value": "ROLE2"
}
]
}],
"structDefs": [],
"classificationDefs": [],
"entityDefs": [{
"name": "Contact",
"description": "Contact test. ",
"superTypes": [
"Referenceable"
],
"serviceType": "workflow",
"typeVersion": "1.0",
"attributeDefs": [{
"name": "name",
"typeName": "string",
"cardinality": "SINGLE",
"isIndexable": true,
"isOptional": true,
"isUnique": false
},
{
"name": "role",
"typeName": "Role",
"cardinality": "SINGLE",
"isIndexable": false,
"isOptional": true,
"isUnique": false
}
]
},
{
"name": "Organization",
"description": "organization ",
"superTypes": [
"Referenceable"
],
"serviceType": "workflow",
"typeVersion": "1.0",
"attributeDefs": [{
"name": "organizationCode",
"typeName": "string",
"cardinality": "SINGLE",
"isIndexable": true,
"isOptional": false,
"isUnique": false
},
{
"name": "organizationName",
"typeName": "string",
"cardinality": "SINGLE",
"isIndexable": true,
"isOptional": false,
"isUnique": false
}
]
}
],
"relationshipDefs": [{
"name": "organization_contacts",
"relationshipCategory": "AGGREGATION",
"propagateTags": "NONE",
"endDef1": {
"type": "Organization",
"name": "contacts",
"isContainer": true,
"cardinality": "SET",
"isLegacyAttribute": false
},
"endDef2": {
"type": "Contact",
"name": "organization",
"isContainer": false,
"cardinality": "SINGLE",
"isLegacyAttribute": false
}
}]
} {code}
> Dsl search with non-primitive attribute
> ---
>
> Key: ATLAS-4557
> URL: https://issues.apache.org/jira/browse/ATLAS-4557
> Project: Atlas
> Issue Type: Wish
> Components: atlas-webui
>Affects Versions: 2.2.0
>Reporter: Hatice Ekenek
>Priority: Critical
>
> Hi,
> I have the following types.
> I want to list the contacts by filtering them according to the organization
> property. But I can't find the right method to do this. I would be glad if
> you help.
> dsl query example:
> Contact where organization.__guid = "d44532ea-c6fc-417b-8c59-f988777dd51f"
>
> Example entity types:
> Contact Entity:
> {
> "name": "Contact",
> "description": "Contact test. ",
> "superTypes": [
> "Referenceable"
> ],
> "serviceType": "workflow",
> "typeVersion": "1.0",
> "attributeDefs": [
> {
> "name": "name",
> "typeName": "string",
> "cardinality": "SINGLE",
> "isIndexable": true,
> "isOptional": true,
> "isUnique": false
> },
> {
> "name": "organization",
> "typeName": "Organization",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": false,
> "isUnique": false
> },
> {
> "name": "role",
> "typeName": "Role",
> "cardinality": "SINGLE",
> "isIndexable": false,
> "isOptional": true,
> "isUnique": false
> }
> ]
> }
>
> Organization Entity Type:
>
> {
> "name": "Organization",
> "description": "organization ",
> "superTypes": [
>
[jira] [Updated] (ATLAS-4551) Add maven jacoco plugin for code coverage
[ https://issues.apache.org/jira/browse/ATLAS-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4551: -- Attachment: target_site_jacoco_index.html.png > Add maven jacoco plugin for code coverage > - > > Key: ATLAS-4551 > URL: https://issues.apache.org/jira/browse/ATLAS-4551 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Attachments: target_site_jacoco_index.html.png > > > Jacoco maven plugin generates test coverage report by measuring *lines of > code exercised during the tests* > *Step* > mvn clean install > *Report* > report will be generated in /target/site/jacoco directory of each module. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4551) Add maven jacoco plugin for code coverage
[ https://issues.apache.org/jira/browse/ATLAS-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4551: -- Attachment: (was: Screenshot from 2022-02-09 20-11-52.png) > Add maven jacoco plugin for code coverage > - > > Key: ATLAS-4551 > URL: https://issues.apache.org/jira/browse/ATLAS-4551 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > Jacoco maven plugin generates test coverage report by measuring *lines of > code exercised during the tests* > *Step* > mvn clean install > *Report* > report will be generated in /target/site/jacoco directory of each module. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4551) Add maven jacoco plugin for code coverage
[ https://issues.apache.org/jira/browse/ATLAS-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4551: -- Attachment: Screenshot from 2022-02-09 20-11-52.png > Add maven jacoco plugin for code coverage > - > > Key: ATLAS-4551 > URL: https://issues.apache.org/jira/browse/ATLAS-4551 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > Jacoco maven plugin generates test coverage report by measuring *lines of > code exercised during the tests* > *Step* > mvn clean install > *Report* > report will be generated in /target/site/jacoco directory of each module. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ATLAS-4551) Add maven jacoco plugin for code coverage
Pinal Shah created ATLAS-4551: - Summary: Add maven jacoco plugin for code coverage Key: ATLAS-4551 URL: https://issues.apache.org/jira/browse/ATLAS-4551 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah Jacoco maven plugin generates test coverage report by measuring *lines of code exercised during the tests* *Step* mvn clean install *Report* report will be generated in /target/site/jacoco directory of each module. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4467) Basic Search : Search with type Asset takes long time to respond
[ https://issues.apache.org/jira/browse/ATLAS-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4467: -- Description: As the subTypes of Asset type is growing, the basic search query length to search with 'Asset' and all subTypes increases. Basic Search has validation on query length < 512 (atlas.graph.index.search.types.max-query-str-length) to search through indexes, beyond which it will use graph query *WorkAround* Increase the query length to greater value. was: As the subTypes of Asset type is growing, the basic search query length to search with 'Asset' and all subTypes increases. Basic Search has validation on query length < 512 (atlas.graph.index.search.types.max-query-str-length) to search through indexes, beyond which it will use graph query > Basic Search : Search with type Asset takes long time to respond > > > Key: ATLAS-4467 > URL: https://issues.apache.org/jira/browse/ATLAS-4467 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > As the subTypes of Asset type is growing, the basic search query length to > search with 'Asset' and all subTypes increases. > Basic Search has validation on query length < 512 > (atlas.graph.index.search.types.max-query-str-length) to search through > indexes, beyond which it will use graph query > *WorkAround* > Increase the query length to greater value. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (ATLAS-4531) _ALL_ENTITY_TYPES showing same basic search results even when offset is changed
[ https://issues.apache.org/jira/browse/ATLAS-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah reassigned ATLAS-4531: - Assignee: Pinal Shah > _ALL_ENTITY_TYPES showing same basic search results even when offset is > changed > --- > > Key: ATLAS-4531 > URL: https://issues.apache.org/jira/browse/ATLAS-4531 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Pinal Shah >Priority: Minor > > Whenever we fire a basic search for _ALL_ENTITY_TYPES, the same set of > results are always fetched even if you change the offset. > For ex: > If these are the results when you select page limit as 2 and offset as 0 > (there are total 59 results): > x1 > x2 > Then on increasing the offset to 3 you still get the above results x1 and x2. > This only occurs for _ALL_ENTITY_TYPES. If you search for specific data types > like hive_table and others the behaviour is normal. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (ATLAS-3606) Hive Hook: Missing HIVE_PROCESS attribute values
[ https://issues.apache.org/jira/browse/ATLAS-3606 ] Pinal Shah deleted comment on ATLAS-3606: --- was (Author: pinal.shah): Out of above properties, 'userName', 'queryId', 'queryText' will be available in *hive_process_execution* entity and are not intended to be in *hive_process* entity > Hive Hook: Missing HIVE_PROCESS attribute values > > > Key: ATLAS-3606 > URL: https://issues.apache.org/jira/browse/ATLAS-3606 > Project: Atlas > Issue Type: Bug >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: > 0001-ATLAS-3606-Missing-HIVE_PROCESS-attribute-values-in-.patch, > ATLAS-3606.patch > > > In Hive Producer, When hive_process entity gets created during many > operations eg. "CREATETABLE", "CREATETABLE_AS_SELECT " > userName=, > queryId=, > clusterName= > queryText= > values are missing. This attributes were not added due to ATLAS-3133. > Now this attributes can be added in hive_process by enabling the below > property > *atlas.hook.hive.hive_process.populate.deprecated.attributes =true* > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ATLAS-4529) DSL Search : OrderBy does not work for ScriptEngineBasedExecutor (gremlin groovy)
[
https://issues.apache.org/jira/browse/ATLAS-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4529:
--
Fix Version/s: 3.0.0
2.3.0
> DSL Search : OrderBy does not work for ScriptEngineBasedExecutor (gremlin
> groovy)
> -
>
> Key: ATLAS-4529
> URL: https://issues.apache.org/jira/browse/ATLAS-4529
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> When below property is changed to 'false', order by doesn't work
> {code:java}
> atlas.dsl.executor.traversal=false{code}
> {code:java}
> curl -k -u :
> 'http://<>/api/atlas/v2/search/dsl?limit=25&offset=0&query=orderby%20name%20desc&typeName=hdfs_path'
> {"errorCode":"ATLAS-500-00-00A","errorMessage":"Gremlin script execution
> failed: g.V().has('__typeName', 'hdfs_path').order().by('Asset.__s_name',
> decr).dedup().limit(25).toList()","errorCause":"javax.script.ScriptException:
> groovy.lang.MissingPropertyException: No such property: decr for class:
> Script15"}
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ATLAS-4529) DSL Search : OrderBy does not work for ScriptEngineBasedExecutor (gremlin groovy)
[
https://issues.apache.org/jira/browse/ATLAS-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4529:
--
Description:
When below property is changed to 'false', order by doesn't work
{code:java}
atlas.dsl.executor.traversal=false{code}
{code:java}
curl -k -u :
'http://<>/api/atlas/v2/search/dsl?limit=25&offset=0&query=orderby%20name%20desc&typeName=hdfs_path'
{"errorCode":"ATLAS-500-00-00A","errorMessage":"Gremlin script execution
failed: g.V().has('__typeName', 'hdfs_path').order().by('Asset.__s_name',
decr).dedup().limit(25).toList()","errorCause":"javax.script.ScriptException:
groovy.lang.MissingPropertyException: No such property: decr for class:
Script15"}
{code}
was:
When below property is changed to 'false', order by doesn't work
atlas.dsl.executor.traversal=false
curl -k -u :
'http://<>/api/atlas/v2/search/dsl?limit=25&offset=0&query=orderby%20name%20desc&typeName=hdfs_path'{"errorCode":"ATLAS-500-00-00A","errorMessage":"Gremlin
script execution failed: g.V().has('__typeName',
'hdfs_path').order().by('Asset.__s_name',
decr).dedup().limit(25).toList()","errorCause":"javax.script.ScriptException:
groovy.lang.MissingPropertyException: No such property: decr for class:
Script15"}
> DSL Search : OrderBy does not work for ScriptEngineBasedExecutor (gremlin
> groovy)
> -
>
> Key: ATLAS-4529
> URL: https://issues.apache.org/jira/browse/ATLAS-4529
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>
> When below property is changed to 'false', order by doesn't work
> {code:java}
> atlas.dsl.executor.traversal=false{code}
> {code:java}
> curl -k -u :
> 'http://<>/api/atlas/v2/search/dsl?limit=25&offset=0&query=orderby%20name%20desc&typeName=hdfs_path'
> {"errorCode":"ATLAS-500-00-00A","errorMessage":"Gremlin script execution
> failed: g.V().has('__typeName', 'hdfs_path').order().by('Asset.__s_name',
> decr).dedup().limit(25).toList()","errorCause":"javax.script.ScriptException:
> groovy.lang.MissingPropertyException: No such property: decr for class:
> Script15"}
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ATLAS-4529) DSL Search : OrderBy does not work for ScriptEngineBasedExecutor (gremlin groovy)
Pinal Shah created ATLAS-4529:
-
Summary: DSL Search : OrderBy does not work for
ScriptEngineBasedExecutor (gremlin groovy)
Key: ATLAS-4529
URL: https://issues.apache.org/jira/browse/ATLAS-4529
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
When below property is changed to 'false', order by doesn't work
atlas.dsl.executor.traversal=false
curl -k -u :
'http://<>/api/atlas/v2/search/dsl?limit=25&offset=0&query=orderby%20name%20desc&typeName=hdfs_path'{"errorCode":"ATLAS-500-00-00A","errorMessage":"Gremlin
script execution failed: g.V().has('__typeName',
'hdfs_path').order().by('Asset.__s_name',
decr).dedup().limit(25).toList()","errorCause":"javax.script.ScriptException:
groovy.lang.MissingPropertyException: No such property: decr for class:
Script15"}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ATLAS-4459) Fix solr indexes for testcases failures
[ https://issues.apache.org/jira/browse/ATLAS-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4459: -- Fix Version/s: 2.3.0 3.0.0 > Fix solr indexes for testcases failures > --- > > Key: ATLAS-4459 > URL: https://issues.apache.org/jira/browse/ATLAS-4459 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Labels: Testing > Fix For: 3.0.0, 2.3.0 > > Attachments: ATLAS-4459.patch > > > Fixing solr indexes which are used for the testcases in solrConfig.xml > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4454) Upgrade JanusGraph version to 0.6.0
[ https://issues.apache.org/jira/browse/ATLAS-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4454: -- Fix Version/s: 2.3.0 3.0.0 > Upgrade JanusGraph version to 0.6.0 > --- > > Key: ATLAS-4454 > URL: https://issues.apache.org/jira/browse/ATLAS-4454 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > Upgrading janusgraph version - 0.6.0 > Upgrading tinkerpop version - 3.5.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4467) Basic Search : Search with type Asset takes long time to respond
Pinal Shah created ATLAS-4467: - Summary: Basic Search : Search with type Asset takes long time to respond Key: ATLAS-4467 URL: https://issues.apache.org/jira/browse/ATLAS-4467 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah As the subTypes of Asset type is growing, the basic search query length to search with 'Asset' and all subTypes increases. Basic Search has validation on query length < 512 (atlas.graph.index.search.types.max-query-str-length) to search through indexes, beyond which it will use graph query -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4459) Fix solr indexes for testcases failures
[ https://issues.apache.org/jira/browse/ATLAS-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4459: -- Attachment: ATLAS-4459.patch > Fix solr indexes for testcases failures > --- > > Key: ATLAS-4459 > URL: https://issues.apache.org/jira/browse/ATLAS-4459 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Labels: Testing > Attachments: ATLAS-4459.patch > > > Fixing solr indexes which are used for the testcases in solrConfig.xml > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4459) Fix solr indexes for testcases failures
[ https://issues.apache.org/jira/browse/ATLAS-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4459: -- Labels: Testing (was: ) > Fix solr indexes for testcases failures > --- > > Key: ATLAS-4459 > URL: https://issues.apache.org/jira/browse/ATLAS-4459 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Labels: Testing > > Fixing solr indexes which are used for the testcases in solrConfig.xml > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4459) Fix solr indexes for testcases failures
Pinal Shah created ATLAS-4459: - Summary: Fix solr indexes for testcases failures Key: ATLAS-4459 URL: https://issues.apache.org/jira/browse/ATLAS-4459 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah Fixing solr indexes which are used for the testcases in solrConfig.xml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4454) Upgrade JanusGraph version to 0.6.0
[ https://issues.apache.org/jira/browse/ATLAS-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4454: -- Description: Upgrading janusgraph version - 0.6.0 Upgrading tinkerpop version - 3.5.1 > Upgrade JanusGraph version to 0.6.0 > --- > > Key: ATLAS-4454 > URL: https://issues.apache.org/jira/browse/ATLAS-4454 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > Upgrading janusgraph version - 0.6.0 > Upgrading tinkerpop version - 3.5.1 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4454) Upgrade JanusGraph version to 0.6.0
Pinal Shah created ATLAS-4454: - Summary: Upgrade JanusGraph version to 0.6.0 Key: ATLAS-4454 URL: https://issues.apache.org/jira/browse/ATLAS-4454 Project: Atlas Issue Type: Task Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4447) Update Composite indexes Schema Status
[ https://issues.apache.org/jira/browse/ATLAS-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4447: -- Fix Version/s: 2.3.0 3.0.0 > Update Composite indexes Schema Status > -- > > Key: ATLAS-4447 > URL: https://issues.apache.org/jira/browse/ATLAS-4447 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > This patch repairs the composite indexes which are in REGISTERED state to > enable status -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4447) Update Composite indexes Schema Status
[ https://issues.apache.org/jira/browse/ATLAS-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4447: -- Description: This patch repairs the composite indexes which are in REGISTERED state to enable status (was: This patch repairs the composite indexes which are in REGISTERED state) > Update Composite indexes Schema Status > -- > > Key: ATLAS-4447 > URL: https://issues.apache.org/jira/browse/ATLAS-4447 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > This patch repairs the composite indexes which are in REGISTERED state to > enable status -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4447) Update Composite indexes Schema Status
[ https://issues.apache.org/jira/browse/ATLAS-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4447: -- Summary: Update Composite indexes Schema Status (was: Repair Composite Indexes) > Update Composite indexes Schema Status > -- > > Key: ATLAS-4447 > URL: https://issues.apache.org/jira/browse/ATLAS-4447 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > This patch repairs the composite indexes which are in REGISTERED state -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4447) Repair Composite Indexes
Pinal Shah created ATLAS-4447: - Summary: Repair Composite Indexes Key: ATLAS-4447 URL: https://issues.apache.org/jira/browse/ATLAS-4447 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah This patch repairs the composite indexes which are in REGISTERED state -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4442) Support Relationship search
[
https://issues.apache.org/jira/browse/ATLAS-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4442:
--
Description:
*Current Working :*
Atlas is entirely entity-based – it is not possible to search for relationships.
*Improvement :*
Get all relationships (edges) for particular relationship type, having some
criteria on its properties
*Example :*
Get all the relations matching
{code:java}
type = rel_type and edge_property1 = edge_value1
{code}
*Request Payload :*
{"relationshipName" : "rel_type",
"relationshipFilters": { "condition": "OR", "criterion": [
{ "attributeName": "{{edge_property1}}", "operator": "eq",
"attributeValue": "{{edge_value1}}" }
] },
"limit":25,
"offset":0 }
was:
*Current Working :*
Atlas is entirely entity-based – it is not possible to search for relationships.
*Improvement :*
Get all relationships (edges) for particular relationship type, having some
criteria on its properties
*Example :
* {{Get all relations matching type = rel_type and edge_property1 =
edge_value1}}
*Request Payload :*
{"relationshipName" : "rel_type",
"relationshipFilters": { "condition": "OR", "criterion": [
{ "attributeName": "{{edge_property1}}", "operator": "eq",
"attributeValue": "{{edge_value1}}" }
] },
"limit":25,
"offset":0 }
> Support Relationship search
> ---
>
> Key: ATLAS-4442
> URL: https://issues.apache.org/jira/browse/ATLAS-4442
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>
> *Current Working :*
> Atlas is entirely entity-based – it is not possible to search for
> relationships.
> *Improvement :*
> Get all relationships (edges) for particular relationship type, having some
> criteria on its properties
> *Example :*
> Get all the relations matching
> {code:java}
> type = rel_type and edge_property1 = edge_value1
> {code}
> *Request Payload :*
> {"relationshipName" : "rel_type",
> "relationshipFilters": { "condition": "OR", "criterion": [
> { "attributeName": "{{edge_property1}}", "operator": "eq",
> "attributeValue": "{{edge_value1}}" }
> ] },
> "limit":25,
> "offset":0 }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4442) Support Relationship search
[
https://issues.apache.org/jira/browse/ATLAS-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4442:
--
Description:
*Current Working :*
Atlas is entirely entity-based – it is not possible to search for relationships.
*Improvement :*
Get all relationships (edges) for particular relationship type, having some
criteria on its properties
*Example :
* {{Get all relations matching type = rel_type and edge_property1 =
edge_value1}}
*Request Payload :*
{"relationshipName" : "rel_type",
"relationshipFilters": { "condition": "OR", "criterion": [
{ "attributeName": "{{edge_property1}}", "operator": "eq",
"attributeValue": "{{edge_value1}}" }
] },
"limit":25,
"offset":0 }
was:
*Current Working :*
Atlas is entirely entity-based – it is not possible to search for relationships.
*Improvement :*
Get all relationships (edges) for particular relationship type, having some
criteria on its properties
*Example :
* {{Get all relations matching type = rel_type and edge_property1 =
edge_value1}}
*Request Payload :*
{"relationshipName" : "rel_type",
"relationshipFilters": \{ "condition": "OR", "criterion": [{
"attributeName": "post_name", "operator": "contains",
"attributeValue": "jay", "typeName":"user_post" }] },
"limit":25,
"offset":0 }
{{}}
> Support Relationship search
> ---
>
> Key: ATLAS-4442
> URL: https://issues.apache.org/jira/browse/ATLAS-4442
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>
> *Current Working :*
> Atlas is entirely entity-based – it is not possible to search for
> relationships.
> *Improvement :*
> Get all relationships (edges) for particular relationship type, having some
> criteria on its properties
> *Example :
> * {{Get all relations matching type = rel_type and edge_property1 =
> edge_value1}}
> *Request Payload :*
> {"relationshipName" : "rel_type",
> "relationshipFilters": { "condition": "OR", "criterion": [
> { "attributeName": "{{edge_property1}}", "operator": "eq",
> "attributeValue": "{{edge_value1}}" }
> ] },
> "limit":25,
> "offset":0 }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4442) Support Relationship search
Pinal Shah created ATLAS-4442:
-
Summary: Support Relationship search
Key: ATLAS-4442
URL: https://issues.apache.org/jira/browse/ATLAS-4442
Project: Atlas
Issue Type: Improvement
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
*Current Working :*
Atlas is entirely entity-based – it is not possible to search for relationships.
*Improvement :*
Get all relationships (edges) for particular relationship type, having some
criteria on its properties
*Example :
* {{Get all relations matching type = rel_type and edge_property1 =
edge_value1}}
*Request Payload :*
{"relationshipName" : "rel_type",
"relationshipFilters": \{ "condition": "OR", "criterion": [{
"attributeName": "post_name", "operator": "contains",
"attributeValue": "jay", "typeName":"user_post" }] },
"limit":25,
"offset":0 }
{{}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4436) Basic Search : Search By Query '*' gets internal entities also
Pinal Shah created ATLAS-4436: - Summary: Basic Search : Search By Query '*' gets internal entities also Key: ATLAS-4436 URL: https://issues.apache.org/jira/browse/ATLAS-4436 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Pinal Shah Steps to Reproduce: - Remove Search By Type - Add '*' in Search By Query and Click on Search Actual : It brings all the internal entities like '__AtlasAuditEntry' etc Expected : It should not show internal types -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4422) Quick Search: Provide sorting
[
https://issues.apache.org/jira/browse/ATLAS-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4422:
--
Fix Version/s: 2.3.0
3.0.0
> Quick Search: Provide sorting
> -
>
> Key: ATLAS-4422
> URL: https://issues.apache.org/jira/browse/ATLAS-4422
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
> Labels: quicksearch
> Fix For: 3.0.0, 2.3.0
>
>
> *Improvement:* This will add a sorting functionality in quick search API and
> get the result list in Sorted manner.
> *Note:* Result will be sorted only when 'typeName' has a valid entity type
> name as a value.
> *Example:*
> {code:java}
> { "query":"sales",
> "typeName":"Asset",
> "sortBy":"__typeName",
> "sortOrder":"ASCENDING" }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4422) Quick Search: Provide sorting
[
https://issues.apache.org/jira/browse/ATLAS-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4422:
--
Labels: quicksearch (was: )
> Quick Search: Provide sorting
> -
>
> Key: ATLAS-4422
> URL: https://issues.apache.org/jira/browse/ATLAS-4422
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
> Labels: quicksearch
>
> *Improvement:* This will add a sorting functionality in quick search API and
> get the result list in Sorted manner.
> *Note:* Result will be sorted only when 'typeName' has a valid entity type
> name as a value.
> *Example:*
> {code:java}
> { "query":"sales",
> "typeName":"Asset",
> "sortBy":"__typeName",
> "sortOrder":"ASCENDING" }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4422) Quick Search: Provide sorting
Pinal Shah created ATLAS-4422:
-
Summary: Quick Search: Provide sorting
Key: ATLAS-4422
URL: https://issues.apache.org/jira/browse/ATLAS-4422
Project: Atlas
Issue Type: Improvement
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
*Improvement:* This will add a sorting functionality in quick search API and
get the result list in Sorted manner.
*Note:* Result will be sorted only when 'typeName' has a valid entity type name
as a value.
*Example:*
{code:java}
{ "query":"sales",
"typeName":"Asset",
"sortBy":"__typeName",
"sortOrder":"ASCENDING" }
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4096) Quick Search : Search with query text containing space returns no records.
[ https://issues.apache.org/jira/browse/ATLAS-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah resolved ATLAS-4096. --- Resolution: Fixed > Quick Search : Search with query text containing space returns no records. > -- > > Key: ATLAS-4096 > URL: https://issues.apache.org/jira/browse/ATLAS-4096 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.1.0 >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > Labels: quicksearch > Attachments: Screenshot from 2021-01-07 14-00-05.png, Screenshot from > 2021-01-07 14-00-22.png > > > Selected ml_model_build entity type where some entity names contain space. > E.g. "Simple Model 158" > When the "search by Text" added as "Simple*". It returned 8 records > containing space in the entities name. But when changed to "Simple Model*" > returned no records. > Attached the screenshots for the above 2 scenarios. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3678) User defined properties are not listed under suggestions
[ https://issues.apache.org/jira/browse/ATLAS-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah resolved ATLAS-3678. --- Resolution: Not A Bug > User defined properties are not listed under suggestions > > > Key: ATLAS-3678 > URL: https://issues.apache.org/jira/browse/ATLAS-3678 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 2.1.0, 3.0.0 >Reporter: Umesh Padashetty >Assignee: Pinal Shah >Priority: Minor > Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot > 2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, > Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 > PM.png > > > When user-defined properties are added to an entity, and when we type the > "user-defined property" in the global search bar, the expectation is that > # The corresponding entity appears in the quick search, entities dropdown. > This is working > # The user-defined property itself should appear in the suggestions > dropdown. This is not working > Tried similar tests with labels, entities that are tagged with labels appear > in the quick search drop down, and the labels itself appear as part of the > suggestions. Attached are the screenshots. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-3678) User defined properties are not listed under suggestions
[ https://issues.apache.org/jira/browse/ATLAS-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399753#comment-17399753 ] Pinal Shah edited comment on ATLAS-3678 at 8/17/21, 8:19 AM: - This issue is because search weight for the user-defined attributes is kept low. Workaround: increase search weight of custom attributes greater than or equal to 8 (MIN_SEARCH_WEIGHT_FOR_SUGGESTIONS) was (Author: pinal.shah): This issue is because search weight for the user-defined attributes is kept low. > User defined properties are not listed under suggestions > > > Key: ATLAS-3678 > URL: https://issues.apache.org/jira/browse/ATLAS-3678 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 2.1.0, 3.0.0 >Reporter: Umesh Padashetty >Assignee: Pinal Shah >Priority: Minor > Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot > 2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, > Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 > PM.png > > > When user-defined properties are added to an entity, and when we type the > "user-defined property" in the global search bar, the expectation is that > # The corresponding entity appears in the quick search, entities dropdown. > This is working > # The user-defined property itself should appear in the suggestions > dropdown. This is not working > Tried similar tests with labels, entities that are tagged with labels appear > in the quick search drop down, and the labels itself appear as part of the > suggestions. Attached are the screenshots. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3682) Multivalued attributes are not listed under Business Metadata Attribute filter
[ https://issues.apache.org/jira/browse/ATLAS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-3682: -- Issue Type: Improvement (was: Bug) > Multivalued attributes are not listed under Business Metadata Attribute filter > -- > > Key: ATLAS-3682 > URL: https://issues.apache.org/jira/browse/ATLAS-3682 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 2.1.0, 3.0.0 >Reporter: Umesh Padashetty >Assignee: Pinal Shah >Priority: Major > Attachments: Screenshot 2020-03-24 at 1.01.54 AM.png, Screenshot > 2020-03-24 at 1.02.28 AM.png > > > Added attributes of different types, noticed that the multi valued attributes > are bot being listed for an entity filter, even when the attribute is > applicable to that entity. Screenshots attached below. > As you can see, the attribute "Reviewed by" which is of type "array" > is not being listed under the Business Metadata Attribute drop down. > CC: [~kevalbhatt] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3682) Multivalued attributes are not listed under Business Metadata Attribute filter
[ https://issues.apache.org/jira/browse/ATLAS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-3682: -- Labels: BasicSearch (was: ) > Multivalued attributes are not listed under Business Metadata Attribute filter > -- > > Key: ATLAS-3682 > URL: https://issues.apache.org/jira/browse/ATLAS-3682 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Affects Versions: 2.1.0, 3.0.0 >Reporter: Umesh Padashetty >Assignee: Pinal Shah >Priority: Major > Labels: BasicSearch > Attachments: Screenshot 2020-03-24 at 1.01.54 AM.png, Screenshot > 2020-03-24 at 1.02.28 AM.png > > > Added attributes of different types, noticed that the multi valued attributes > are bot being listed for an entity filter, even when the attribute is > applicable to that entity. Screenshots attached below. > As you can see, the attribute "Reviewed by" which is of type "array" > is not being listed under the Business Metadata Attribute drop down. > CC: [~kevalbhatt] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3678) User defined properties are not listed under suggestions
[ https://issues.apache.org/jira/browse/ATLAS-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399753#comment-17399753 ] Pinal Shah commented on ATLAS-3678: --- This issue is because search weight for the user-defined attributes is kept low. > User defined properties are not listed under suggestions > > > Key: ATLAS-3678 > URL: https://issues.apache.org/jira/browse/ATLAS-3678 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Affects Versions: 2.1.0, 3.0.0 >Reporter: Umesh Padashetty >Assignee: Pinal Shah >Priority: Minor > Attachments: Screenshot 2020-03-23 at 2.56.49 PM.png, Screenshot > 2020-03-23 at 2.57.57 PM.png, Screenshot 2020-03-23 at 2.58.57 PM.png, > Screenshot 2020-03-23 at 3.00.27 PM.png, Screenshot 2020-03-23 at 3.00.39 > PM.png > > > When user-defined properties are added to an entity, and when we type the > "user-defined property" in the global search bar, the expectation is that > # The corresponding entity appears in the quick search, entities dropdown. > This is working > # The user-defined property itself should appear in the suggestions > dropdown. This is not working > Tried similar tests with labels, entities that are tagged with labels appear > in the quick search drop down, and the labels itself appear as part of the > suggestions. Attached are the screenshots. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-2989) Full text search based dsl query is not bringing the results appropriately
[ https://issues.apache.org/jira/browse/ATLAS-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17395966#comment-17395966 ] Pinal Shah commented on ATLAS-2989: --- Also can you mention the affect version? > Full text search based dsl query is not bringing the results appropriately > -- > > Key: ATLAS-2989 > URL: https://issues.apache.org/jira/browse/ATLAS-2989 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Abhishek Sharma >Priority: Blocker > > Hello > I have created some entities(like test1,school,college) using custom type > that I have prepared. > Each entity contains array of columns .Each column contains array of sources. > Each Column comprises of columnAlias as a field. > Now when I am performing the full text search using the below mentioned query > [http://172.29.59.59:21000/api/atlas/v2/search/fulltext?excludeDeletedEntities=true&query=key+where+key='c1'|http://172.29.59.59:21000/api/atlas/v2/search/fulltext?excludeDeletedEntities=true&query=key+where+key=%27c1%27] > Even if I provide the key to be something which is not correct and irrevelant > ,it is still showing output and it is showing output even on passing correct > key. > I have the following doubts - > 1) Whether my syntax for full text search query is incorrect ? > 2) Same pattern is observed even on querying using basic dsl > http://172.29.59.81:21000/api/atlas/v2/search/basic?excludeDeletedEntities=true&typeName=&query=columns -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-2989) Full text search based dsl query is not bringing the results appropriately
[ https://issues.apache.org/jira/browse/ATLAS-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17395965#comment-17395965 ] Pinal Shah commented on ATLAS-2989: --- [~abhi63269] Full text search is not preferred to query like dsl (Ex: where Key = value). You can use DSL query/ Advanced search REST api for it. > Full text search based dsl query is not bringing the results appropriately > -- > > Key: ATLAS-2989 > URL: https://issues.apache.org/jira/browse/ATLAS-2989 > Project: Atlas > Issue Type: Bug > Components: atlas-core, atlas-webui >Reporter: Abhishek Sharma >Priority: Blocker > > Hello > I have created some entities(like test1,school,college) using custom type > that I have prepared. > Each entity contains array of columns .Each column contains array of sources. > Each Column comprises of columnAlias as a field. > Now when I am performing the full text search using the below mentioned query > [http://172.29.59.59:21000/api/atlas/v2/search/fulltext?excludeDeletedEntities=true&query=key+where+key='c1'|http://172.29.59.59:21000/api/atlas/v2/search/fulltext?excludeDeletedEntities=true&query=key+where+key=%27c1%27] > Even if I provide the key to be something which is not correct and irrevelant > ,it is still showing output and it is showing output even on passing correct > key. > I have the following doubts - > 1) Whether my syntax for full text search query is incorrect ? > 2) Same pattern is observed even on querying using basic dsl > http://172.29.59.81:21000/api/atlas/v2/search/basic?excludeDeletedEntities=true&typeName=&query=columns -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-2990) Full text search not working as expected
[ https://issues.apache.org/jira/browse/ATLAS-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17395960#comment-17395960 ] Pinal Shah commented on ATLAS-2990: --- [~abhi63269] If you want to search with query language (Domain specific search language) you can use DSL search/ Advanced search REST api. Example : /api/atlas/v2/search/dsl?limit=25&offset=0&query=hive_table%20where%20name%20%3D%20%27testMap%27 > Full text search not working as expected > > > Key: ATLAS-2990 > URL: https://issues.apache.org/jira/browse/ATLAS-2990 > Project: Atlas > Issue Type: Bug >Reporter: Abhishek Sharma >Priority: Blocker > > Hello, > I am performing full text search on my entities. My entity structure has > array of columns inside it. Now each column has a set of attributes inside > it. When I do full text search based on the particular attribute of the > column then I get all the entities that I created from the type despite the > filtering condition applied in the form of where clause. > It looks like the where clause is not even working with the full text search. > Here is my sample query- > api/atlas/v2/search/fulltext?query=%2C+columns+where+%3D%27%27 > > Now in the above query I only want the entities where the attribute is equal > to value but instead the full text search retrieves all the entities of the > type despite where clause is satisfied or not. > > Please suggest me if I am using the full text query with wrong syntax > Or if you could provide some other DSL query that solves my problem statement > then I would be really thankful. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4386) Relationship search: Sorting does not work when relationship label is passed
[ https://issues.apache.org/jira/browse/ATLAS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4386: -- Summary: Relationship search: Sorting does not work when relationship label is passed (was: Relationship search: Sorting does not work when passed relationship label) > Relationship search: Sorting does not work when relationship label is passed > > > Key: ATLAS-4386 > URL: https://issues.apache.org/jira/browse/ATLAS-4386 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > Relationship Search is not able to sort when relationship label is passed as > a queryParam instead of attribute. > Example: > [api/atlas/v2/search/relationship?limit=25&offset=0&guid=cca5c29d-307f-4a9b-ac6c-79f41a08a90b&relation=__hive_table.columns&sortBy=name&sortOrder=DESCENDING|http://localhost:21000/api/atlas/v2/search/relationship?limit=25&offset=0&guid=cca5c29d-307f-4a9b-ac6c-79f41a08a90b&relation=Table.DB&sortBy=name&sortOrder=DESCENDING&excludeDeletedEntities=true&includeSubClassifications=true&includeSubTypes=true&includeClassificationAttributes=true&_=1627902986338] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4386) Relationship search: Sorting does not work when passed relationship label
[ https://issues.apache.org/jira/browse/ATLAS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinal Shah updated ATLAS-4386: -- Description: Relationship Search is not able to sort when relationship label is passed as a queryParam instead of attribute. Example: [api/atlas/v2/search/relationship?limit=25&offset=0&guid=cca5c29d-307f-4a9b-ac6c-79f41a08a90b&relation=__hive_table.columns&sortBy=name&sortOrder=DESCENDING|http://localhost:21000/api/atlas/v2/search/relationship?limit=25&offset=0&guid=cca5c29d-307f-4a9b-ac6c-79f41a08a90b&relation=Table.DB&sortBy=name&sortOrder=DESCENDING&excludeDeletedEntities=true&includeSubClassifications=true&includeSubTypes=true&includeClassificationAttributes=true&_=1627902986338] > Relationship search: Sorting does not work when passed relationship label > - > > Key: ATLAS-4386 > URL: https://issues.apache.org/jira/browse/ATLAS-4386 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Pinal Shah >Assignee: Pinal Shah >Priority: Major > > Relationship Search is not able to sort when relationship label is passed as > a queryParam instead of attribute. > Example: > [api/atlas/v2/search/relationship?limit=25&offset=0&guid=cca5c29d-307f-4a9b-ac6c-79f41a08a90b&relation=__hive_table.columns&sortBy=name&sortOrder=DESCENDING|http://localhost:21000/api/atlas/v2/search/relationship?limit=25&offset=0&guid=cca5c29d-307f-4a9b-ac6c-79f41a08a90b&relation=Table.DB&sortBy=name&sortOrder=DESCENDING&excludeDeletedEntities=true&includeSubClassifications=true&includeSubTypes=true&includeClassificationAttributes=true&_=1627902986338] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4386) Relationship search: Sorting does not work when passed relationship label
Pinal Shah created ATLAS-4386: - Summary: Relationship search: Sorting does not work when passed relationship label Key: ATLAS-4386 URL: https://issues.apache.org/jira/browse/ATLAS-4386 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Pinal Shah Assignee: Pinal Shah -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4332) DSL Query : query with like operator and "/" in search text throws 500
Pinal Shah created ATLAS-4332: - Summary: DSL Query : query with like operator and "/" in search text throws 500 Key: ATLAS-4332 URL: https://issues.apache.org/jira/browse/ATLAS-4332 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Pinal Shah hdfs_path name="/warehouse/tablespace/external/hive/db_fdchj.db" returns right entity. hdfs_path name like "/warehouse/*" throws following exception: -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4267) Quick Search : AggregationMetrics is incorrect with some special characters
Pinal Shah created ATLAS-4267: - Summary: Quick Search : AggregationMetrics is incorrect with some special characters Key: ATLAS-4267 URL: https://issues.apache.org/jira/browse/ATLAS-4267 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 3.0.0 Reporter: Pinal Shah Quick search with attribute filter : qualifiedName - beginsWith - "default.datagen_table_sensitive_725_1." has empty AggregationMetrics whereas with "default.datagen_table_sensitive_725_1" has right AggregationMetrics. __ -- This message was sent by Atlassian Jira (v8.3.4#803005)
