[jira] [Commented] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088313#comment-17088313 ] ASF subversion and git services commented on ATLAS-3735: Commit 318c645fb555b17b9fdd8c2f1b642a3065e337fc in atlas's branch refs/heads/master from Ashutosh Mestry [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=318c645 ] ATLAS-3735: CustomAttribute length validation bypass for keys with special prefix. > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088249#comment-17088249 ] Sarath Subramanian commented on ATLAS-3735: --- +1 > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088214#comment-17088214 ] Ashutosh Mestry commented on ATLAS-3735: [~sarath] Attached patch addresses comments above. Thanks for the review! > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3735: --- Attachment: (was: ATLAS-3735-CustomAttribute-length-validation-bypass-.patch) > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3735: --- Attachment: ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088188#comment-17088188 ] Sarath Subramanian commented on ATLAS-3735: --- Review comments: # change 'return' to 'continue' to process other entries in map. # Also if you don't want to enforce any rules (key length, value length, regex) - move the 'if' check after line 2520 (after 'value' assignment) > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3735: --- Attachment: (was: ATLAS-3735-CustomAttribute-length-validation-bypass-.patch) > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3735: --- Attachment: ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3735: --- Attachment: ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Attachments: > ATLAS-3735-CustomAttribute-length-validation-bypass-.patch > > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3735) CustomAttributes: Conditionally Allow Setting of Values Larger than Default Length
[ https://issues.apache.org/jira/browse/ATLAS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3735: --- Attachment: (was: ATLAS-3735-CustomAttribute-length-validation-bypass-.patch) > CustomAttributes: Conditionally Allow Setting of Values Larger than Default > Length > -- > > Key: ATLAS-3735 > URL: https://issues.apache.org/jira/browse/ATLAS-3735 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > > *Background* > The new customAttribute has a limit of set on the default value. This can be > restricting. > *Solution* > * Define special prefix. > * If this is set, bypass the length validation. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3745) [Business Metadata] Newly added BM definitions in admin/BM page are not immediately listed. Refresh is needed to load the new BM definitions.
Umesh Padashetty created ATLAS-3745: --- Summary: [Business Metadata] Newly added BM definitions in admin/BM page are not immediately listed. Refresh is needed to load the new BM definitions. Key: ATLAS-3745 URL: https://issues.apache.org/jira/browse/ATLAS-3745 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 7.26.22 PM.png, Screenshot 2020-04-20 at 7.26.44 PM.png This was working fine before, seems to be a regression. Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3744) [Beta UI] Long entity type filter load time
Umesh Padashetty created ATLAS-3744: --- Summary: [Beta UI] Long entity type filter load time Key: ATLAS-3744 URL: https://issues.apache.org/jira/browse/ATLAS-3744 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 12.57.05 PM.png, Screenshot 2020-04-20 at 12.57.16 PM.png Sometimes, we are taking around 15-20 seconds to load the entity type filters in the new Beta UI when the user clicks on Filters drop down. Once the user clicks on Filters, the UI just freezes there, while the content is loaded in the background. This gives a feeling to the end-user that nothing is happening and the UI is stuck, while in reality it isnt. This is pretty confusing. I think it is a good idea to introduce a loading icon while the data is being loaded in the backend. Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3743) [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes
Umesh Padashetty created ATLAS-3743: --- Summary: [Business Metadata] Multiple issues in Audits tab w.r.t. Entity-Business Metadata attributes Key: ATLAS-3743 URL: https://issues.apache.org/jira/browse/ATLAS-3743 Project: Atlas Issue Type: Bug Components: atlas-core, atlas-webui Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 8.53.54 PM.png, Screenshot 2020-04-20 at 8.54.12 PM.png Following are the issues observed: # All the BM related operations on an entity are listed as BUSINESS_ATTRIBUTE_UPDATE only. Right now, BUSINESS_ATTRIBUTE_UPDATE shows up for all the operations. ## When a BM attribute is added for the first time, ideally BUSINESS_ATTRIBUTE_ADD action should show up. ## On the same lines, when all the BM attributes are removed from entity, BUSINESS_ATTRIBUTE_DELETE should show up. # Internal name, BUSINESS_ATTRIBUTE_UPDATE, is listed as action, instead of plain text like "Business Attribute(s) Updated" # Date type value is shown as timestamp instead of date, in audit/technical properties. Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3742) [Business Metadata] Quick Search/Suggestions does not work with Business metadata attributes, apart from string types
Umesh Padashetty created ATLAS-3742: --- Summary: [Business Metadata] Quick Search/Suggestions does not work with Business metadata attributes, apart from string types Key: ATLAS-3742 URL: https://issues.apache.org/jira/browse/ATLAS-3742 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 7.34.22 PM.png, Screenshot 2020-04-20 at 7.38.33 PM.png, Screenshot 2020-04-20 at 7.38.38 PM.png Business metadata attributes can be defined to be of the following types. * string * boolean * byte * short * int * float * double * long * date * enum Quick search and suggestions works fine only if the business metadata attribute is defined to be of string type. It is not working for any of the other (listed above) BM attribute types we support. Attached screenshots. Also, we support quick search/suggestions on BM Attributes values. So in case of data types like enum, byte, boolean, date etc. how would the user search? For instance, how would the user enter a valid date? what is the valid date format? And for cases like boolean, entering a search text like "true" returns me 100s of returns which are of not much use. Should we support quick search and suggestions on BM attribute names instead of values? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3741) [Business Metadata] Quick Search/Suggestions does not work with multi valued Business metadata attribute
Umesh Padashetty created ATLAS-3741: --- Summary: [Business Metadata] Quick Search/Suggestions does not work with multi valued Business metadata attribute Key: ATLAS-3741 URL: https://issues.apache.org/jira/browse/ATLAS-3741 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 7.12.02 PM.png, Screenshot 2020-04-20 at 7.12.46 PM.png Business metadata attibutes can defined to have multi values. When an attribute which has multi value enabled is added to the entity, the BM attribute assigned entity and the BM attribute value do not apear in neither quick search, nor suggestions. This could be similar to https://issues.apache.org/jira/browse/ATLAS-3682 Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3561) Atlas start fails in embedded-hbase mode with zookeeper error
[
https://issues.apache.org/jira/browse/ATLAS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chaitali borole resolved ATLAS-3561.
Resolution: Fixed
> Atlas start fails in embedded-hbase mode with zookeeper error
> -
>
> Key: ATLAS-3561
> URL: https://issues.apache.org/jira/browse/ATLAS-3561
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Minor
> Fix For: 3.0.0
>
>
> After compiling Atlas with {{mvn clean package -Pdist,embedded-hbase-solr}}
> and starting Atlas with embedded services hbase, solr and kafka using
> {{atlas_start.py}}, the Atlas start fails with below error in
> {{application.log}}
> {noformat}
> 2019-12-09 16:01:28,839 INFO - [main:] ~ Not running setup per configuration
> atlas.server.run.setup.on.start. (SetupSteps$SetupRequired:189)
> 2019-12-09 16:01:32,786 WARN -
> [ReadOnlyZKClient-localhost:2181@0x0fa5f81c-SendThread(localhost:2181):] ~
> Session 0x16eea36b27b0003 for server null, unexpected error, closing socket
> connection and attempting reconnect (ClientCnxn$SendThread:1102)
> java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at
> org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
> at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
> 2019-12-09 16:01:32,889 WARN - [ReadOnlyZKClient-localhost:2181@0x0fa5f81c:]
> ~ 0x0fa5f81c to localhost:2181 failed for get of /hbase/meta-region-server,
> code = CONNECTIONLOSS, retries = 1 (ReadOnlyZKClient$ZKTask$1:183)
> 2019-12-09 16:01:34,004 WARN -
> [ReadOnlyZKClient-localhost:2181@0x0fa5f81c-SendThread(localhost:2181):] ~
> Session 0x16eea36b27b0003 for server null, unexpected error, closing socket
> connection and attempting reconnect (ClientCnxn$SendThread:1102)
> java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at
> org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
> at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
> {noformat}
>
> *Workaround*
> Adding below property in {{hbase-site.xml.template}} and
> running {{mvn clean package -Pdist,embedded-hbase-solr}} the issue is
> resolved.
>
> {code:none}
>
> hbase.unsafe.stream.capability.enforce
> false
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Review Request 72376: ATLAS-3731 : Add Documentation for Apache Atlas 2.1
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72376/ --- (Updated April 20, 2020, 12:43 p.m.) Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sarath Subramanian. Changes --- Added a new BusinessMetadata.md file. Bugs: ATLAS-3731 https://issues.apache.org/jira/browse/ATLAS-3731 Repository: atlas Description --- Updated Documentation for Apache Atlas 2.1 with new improvements and features. Diffs (updated) - docs/src/documents/BusinessMetadata.md PRE-CREATION docs/src/documents/Whats-New/WhatsNew-2.1.md PRE-CREATION Diff: https://reviews.apache.org/r/72376/diff/2/ Changes: https://reviews.apache.org/r/72376/diff/1-2/ Testing --- Thanks, chaitali
[jira] [Created] (ATLAS-3740) [Business Metadata] Suggestions doesn't work correctly with case sensitive Business Metadata attribute values
Umesh Padashetty created ATLAS-3740: --- Summary: [Business Metadata] Suggestions doesn't work correctly with case sensitive Business Metadata attribute values Key: ATLAS-3740 URL: https://issues.apache.org/jira/browse/ATLAS-3740 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 5.23.16 PM.png, Screenshot 2020-04-20 at 5.23.25 PM.png, Screenshot 2020-04-20 at 5.23.34 PM.png, Screenshot 2020-04-20 at 5.23.43 PM.png Entity Details > Business Metadata attributes supports addition of values with case sensitivity. These can be viewed once updated, and later can be edited without any issues. But the problem is, while searching on these attribute values via quick search/suggestions bar, suggestions are being listed only if the user enters these BM attribute values in lower case. If the user enter the case sensitive values as entered in the BM attribute values, there are no suggestions being listed. This works fine with Quick search though. Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3739) [Business Metadata] Suggestions lists Business Metadata attribute values which were previously added and deleted
Umesh Padashetty created ATLAS-3739: --- Summary: [Business Metadata] Suggestions lists Business Metadata attribute values which were previously added and deleted Key: ATLAS-3739 URL: https://issues.apache.org/jira/browse/ATLAS-3739 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Umesh Padashetty Attachments: Screenshot 2020-04-20 at 4.09.35 PM.png, Screenshot 2020-04-20 at 4.09.39 PM.png Since Suggestions work on BM attribute's value. I added few BM attributes to entities (for instance test1a1value, test2a1value, test3a1value) and then later deleted them. But when I search with "test" in the search box, I still see suggestions for test1a1value, test2a1value, test3a1value. Also, when I do click on these suggestions, as expected, it returns empty results. Since there are no entities tagged with this BM attribute value. Quick search works fine though. Attached screenshots. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3738) [Business Metadata] Suggestions does not honour Business Metadata Attribute's Search Weight value
Umesh Padashetty created ATLAS-3738:
---
Summary: [Business Metadata] Suggestions does not honour Business
Metadata Attribute's Search Weight value
Key: ATLAS-3738
URL: https://issues.apache.org/jira/browse/ATLAS-3738
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Umesh Padashetty
Attachments: Screenshot 2020-04-20 at 4.02.28 PM.png, Screenshot
2020-04-20 at 4.02.36 PM.png
In the new Business Metadata UI, the user can provide the search weight for
each attribute. This search weight is used in quick search and suggestions API,
to list the values based on their search weight. An attribute with a search
weight 10 appears before the attribute with a search weight of 9, when they
have the same attribute values.
Defined BM attributes, with search weight in the following order
* Test2A1 = Test2A3 > Test1A1 > Test3A1 > Test4A1
where Test1, Test2... are the Business Metadatas.
Added these BM attributes to the entities with values +value for
better clarity.
As per the functionality, suggestions should be listed in below order when I
enter "test"
* test2a1value
* test2a3value
* test1a1value
* test3a1value
* test4a1value
but they are listed as
* test2a1value
* test3a1value
* test1a1value
* test4a1value
* test2a3value
Quick search, on the other hand, works fine. Also, the following logs were
observed in atlas/application.log when I enter a search pattern in quick
search/suggestion box.
{code:java}
2020-04-20 10:39:15,969 WARN - [etp851765426-201 -
56181e81-11e6-4e02-a23a-d72940f3703c:] ~ Could not convert given VERTEX index
query: [test1a1value] (IndexSerializer:626)
2020-04-20 10:39:15,978 WARN - [etp851765426-201 -
56181e81-11e6-4e02-a23a-d72940f3703c:] ~ Could not convert given VERTEX index
query: [test1a1value] (IndexSerializer:626)
2020-04-20 10:39:24,733 WARN - [etp851765426-160 -
d0030733-2fb9-4dfc-8659-7a3c62415ee0:] ~ Could not convert given VERTEX index
query: [test1a1value*] (IndexSerializer:626)
2020-04-20 10:39:24,784 WARN - [etp851765426-160 -
d0030733-2fb9-4dfc-8659-7a3c62415ee0:] ~ Could not convert given VERTEX index
query: [test1a1value*] (IndexSerializer:626)
2020-04-20 10:39:26,831 WARN - [etp851765426-201 -
7d11aa19-e517-4157-a86c-9ce25a19c1ab:] ~ Could not convert given VERTEX index
query: [te*] (IndexSerializer:626)
2020-04-20 10:39:26,861 WARN - [etp851765426-201 -
7d11aa19-e517-4157-a86c-9ce25a19c1ab:] ~ Could not convert given VERTEX index
query: [te*] (IndexSerializer:626)
2020-04-20 10:39:27,342 WARN - [etp851765426-160 -
66c8be42-f375-4707-bc51-5f0c592828dc:] ~ Could not convert given VERTEX index
query: [test*] (IndexSerializer:626) {code}
Attached screenshots.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-3583) Use Audit framework to generate audit entries for Classification CREATE, UPDATE and DELETE
[ https://issues.apache.org/jira/browse/ATLAS-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane updated ATLAS-3583: --- Component/s: atlas-core > Use Audit framework to generate audit entries for Classification CREATE, > UPDATE and DELETE > -- > > Key: ATLAS-3583 > URL: https://issues.apache.org/jira/browse/ATLAS-3583 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
