[jira] [Commented] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343690#comment-17343690 ] Rahul Kurup commented on ATLAS-4280: +1 > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Labels: Atlas-UI, classification > Attachments: > 0001-ATLAS-4280-UI-Save-button-is-enabled-when-Classifica.patch > > > Previously the Save button in the popup box for classification attribute > would not show as enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4281) Atlas UI: Tasks tab refresh button is seen on other tabs of entity detail page.
[ https://issues.apache.org/jira/browse/ATLAS-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343688#comment-17343688 ] Rahul Kurup commented on ATLAS-4281: +1 > Atlas UI: Tasks tab refresh button is seen on other tabs of entity detail > page. > --- > > Key: ATLAS-4281 > URL: https://issues.apache.org/jira/browse/ATLAS-4281 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Labels: deferred-actions > Attachments: > 0001-ATLAS-4281-Atlas-UI-Tasks-tab-refresh-button-is-seen.patch > > > The refresh button of Tasks tab is seen at the bottom of Properties tab, > Relationships tab, Classification tabs, Audit tab & schema tabs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4274) [Atlas: Glossary] Non matching relation are created via bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4274:
--
Labels: bulk-glossary-import glossary (was: )
> [Atlas: Glossary] Non matching relation are created via bulk import
> ---
>
> Key: ATLAS-4274
> URL: https://issues.apache.org/jira/browse/ATLAS-4274
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Labels: bulk-glossary-import, glossary
> Attachments: ATLAS-4274.patch, Screenshot 2021-05-04 at 3.31.00
> PM.png, Screenshot 2021-05-04 at 3.34.03 PM.png, Screenshot 2021-05-04 at
> 3.34.21 PM.png, Screenshot 2021-05-04 at 3.34.36 PM.png
>
>
> The related terms provided in the input does not match the relation created
> via import
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> a_glossary_1,term_1,,,"a_glossary_1:term_2"
> a_glossary_1,term_2,"a_glossary_1:term_3",,
> a_glossary_1,term_3,,"a_glossary_1:term_1", {code}
> !Screenshot 2021-05-04 at 3.31.00 PM.png|width=1973,height=127!
> !Screenshot 2021-05-04 at 3.34.03 PM.png|width=1038,height=578!
> !Screenshot 2021-05-04 at 3.34.21 PM.png|width=1005,height=563!
> !Screenshot 2021-05-04 at 3.34.36 PM.png|width=541,height=303!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4274) [Atlas: Glossary] Non matching relation are created via bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4274:
--
Component/s: atlas-core
> [Atlas: Glossary] Non matching relation are created via bulk import
> ---
>
> Key: ATLAS-4274
> URL: https://issues.apache.org/jira/browse/ATLAS-4274
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4274.patch, Screenshot 2021-05-04 at 3.31.00
> PM.png, Screenshot 2021-05-04 at 3.34.03 PM.png, Screenshot 2021-05-04 at
> 3.34.21 PM.png, Screenshot 2021-05-04 at 3.34.36 PM.png
>
>
> The related terms provided in the input does not match the relation created
> via import
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> a_glossary_1,term_1,,,"a_glossary_1:term_2"
> a_glossary_1,term_2,"a_glossary_1:term_3",,
> a_glossary_1,term_3,,"a_glossary_1:term_1", {code}
> !Screenshot 2021-05-04 at 3.31.00 PM.png|width=1973,height=127!
> !Screenshot 2021-05-04 at 3.34.03 PM.png|width=1038,height=578!
> !Screenshot 2021-05-04 at 3.34.21 PM.png|width=1005,height=563!
> !Screenshot 2021-05-04 at 3.34.36 PM.png|width=541,height=303!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4274) [Atlas: Glossary] Non matching relation are created via bulk import
[
https://issues.apache.org/jira/browse/ATLAS-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4274:
--
Affects Version/s: 2.1.0
> [Atlas: Glossary] Non matching relation are created via bulk import
> ---
>
> Key: ATLAS-4274
> URL: https://issues.apache.org/jira/browse/ATLAS-4274
> Project: Atlas
> Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Sidharth Kumar Mishra
>Priority: Major
> Attachments: ATLAS-4274.patch, Screenshot 2021-05-04 at 3.31.00
> PM.png, Screenshot 2021-05-04 at 3.34.03 PM.png, Screenshot 2021-05-04 at
> 3.34.21 PM.png, Screenshot 2021-05-04 at 3.34.36 PM.png
>
>
> The related terms provided in the input does not match the relation created
> via import
> {code:java}
> GlossaryName, TermName, ShortDescription, LongDescription, Examples,
> Abbreviation, Usage, AdditionalAttributes, TranslationTerms, ValidValuesFor,
> Synonyms, ReplacedBy, ValidValues, ReplacementTerms, SeeAlso,
> TranslatedTerms, IsA, Antonyms, Classifies, PreferredToTerms, PreferredTerms
> a_glossary_1,term_1,,,"a_glossary_1:term_2"
> a_glossary_1,term_2,"a_glossary_1:term_3",,
> a_glossary_1,term_3,,"a_glossary_1:term_1", {code}
> !Screenshot 2021-05-04 at 3.31.00 PM.png|width=1973,height=127!
> !Screenshot 2021-05-04 at 3.34.03 PM.png|width=1038,height=578!
> !Screenshot 2021-05-04 at 3.34.21 PM.png|width=1005,height=563!
> !Screenshot 2021-05-04 at 3.34.36 PM.png|width=541,height=303!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Review Request 73340: ATLAS-4274: Non matching relation are created via bulk import
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73340/#review222984 --- Ship it! Ship It! - Sarath Subramanian On May 12, 2021, 1 p.m., Sidharth Mishra wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/73340/ > --- > > (Updated May 12, 2021, 1 p.m.) > > > Review request for atlas, Ashutosh Mestry and Sarath Subramanian. > > > Bugs: ATLAS-4274 > https://issues.apache.org/jira/browse/ATLAS-4274 > > > Repository: atlas > > > Description > --- > > ATLAS-4274: Added code to load some terms from graph DB if needed during > glossary import > > > Diffs > - > > repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java > 73217ded3 > repository/src/main/java/org/apache/atlas/glossary/GlossaryTermUtils.java > 553d3d0a6 > > > Diff: https://reviews.apache.org/r/73340/diff/3/ > > > Testing > --- > > Manually tested and confirmed its working as expected. > org.apache.atlas.glossary.GlossaryServiceTest UTs are passing. > > > Thanks, > > Sidharth Mishra > >
[jira] [Updated] (ATLAS-4284) Pruned tables are ignored
[ https://issues.apache.org/jira/browse/ATLAS-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-4284: -- Affects Version/s: 2.1.0 > Pruned tables are ignored > - > > Key: ATLAS-4284 > URL: https://issues.apache.org/jira/browse/ATLAS-4284 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > > Settings in Atlas Server: > atlas.notification.consumer.preprocess.hive_table.prune.pattern=db2.* > No config changes for prune/update made in hive. > With the above settings , created db2.table1. The table is ignored instead of > getting pruned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4284) Pruned tables are ignored
[ https://issues.apache.org/jira/browse/ATLAS-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-4284: -- Labels: hive-hooks (was: ) > Pruned tables are ignored > - > > Key: ATLAS-4284 > URL: https://issues.apache.org/jira/browse/ATLAS-4284 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.1.0 >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > Labels: hive-hooks > Fix For: 3.0.0, 2.2.0 > > > Settings in Atlas Server: > atlas.notification.consumer.preprocess.hive_table.prune.pattern=db2.* > No config changes for prune/update made in hive. > With the above settings , created db2.table1. The table is ignored instead of > getting pruned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4284) Pruned tables are ignored
[ https://issues.apache.org/jira/browse/ATLAS-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-4284: -- Fix Version/s: 2.2.0 3.0.0 > Pruned tables are ignored > - > > Key: ATLAS-4284 > URL: https://issues.apache.org/jira/browse/ATLAS-4284 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.1.0 >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Settings in Atlas Server: > atlas.notification.consumer.preprocess.hive_table.prune.pattern=db2.* > No config changes for prune/update made in hive. > With the above settings , created db2.table1. The table is ignored instead of > getting pruned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4284) Pruned tables are ignored
[ https://issues.apache.org/jira/browse/ATLAS-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343611#comment-17343611 ] ASF subversion and git services commented on ATLAS-4284: Commit 6f45f5f63e3628e3e17b6c94e48ed60d45ad2e9d in atlas's branch refs/heads/branch-2.0 from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=6f45f5f ] ATLAS-4284: Hive pruned tables are ignored and not pruned Signed-off-by: Sarath Subramanian (cherry picked from commit 81888a9c7772b83437d009071e91fbd2a13cc831) > Pruned tables are ignored > - > > Key: ATLAS-4284 > URL: https://issues.apache.org/jira/browse/ATLAS-4284 > Project: Atlas > Issue Type: Bug >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > > Settings in Atlas Server: > atlas.notification.consumer.preprocess.hive_table.prune.pattern=db2.* > No config changes for prune/update made in hive. > With the above settings , created db2.table1. The table is ignored instead of > getting pruned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4284) Pruned tables are ignored
[ https://issues.apache.org/jira/browse/ATLAS-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-4284: -- Component/s: atlas-core > Pruned tables are ignored > - > > Key: ATLAS-4284 > URL: https://issues.apache.org/jira/browse/ATLAS-4284 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.1.0 >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Settings in Atlas Server: > atlas.notification.consumer.preprocess.hive_table.prune.pattern=db2.* > No config changes for prune/update made in hive. > With the above settings , created db2.table1. The table is ignored instead of > getting pruned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-4284) Pruned tables are ignored
[ https://issues.apache.org/jira/browse/ATLAS-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343610#comment-17343610 ] ASF subversion and git services commented on ATLAS-4284: Commit 81888a9c7772b83437d009071e91fbd2a13cc831 in atlas's branch refs/heads/master from Radhika Kundam [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=81888a9 ] ATLAS-4284: Hive pruned tables are ignored and not pruned Signed-off-by: Sarath Subramanian > Pruned tables are ignored > - > > Key: ATLAS-4284 > URL: https://issues.apache.org/jira/browse/ATLAS-4284 > Project: Atlas > Issue Type: Bug >Reporter: Radhika Kundam >Assignee: Radhika Kundam >Priority: Major > > Settings in Atlas Server: > atlas.notification.consumer.preprocess.hive_table.prune.pattern=db2.* > No config changes for prune/update made in hive. > With the above settings , created db2.table1. The table is ignored instead of > getting pruned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-4183) web.xml requires external dtd resource
[ https://issues.apache.org/jira/browse/ATLAS-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deep Singh resolved ATLAS-4183. --- Resolution: Fixed > web.xml requires external dtd resource > -- > > Key: ATLAS-4183 > URL: https://issues.apache.org/jira/browse/ATLAS-4183 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.1.0 >Reporter: Deep Singh >Assignee: Deep Singh >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > We have Servlet 2.3 deployment descriptor (web.xml), which follows J2EE 1.3 > DTDs schema. > Therefore it requires dtd resource hosted at > http://java.sun.com/dtd/web-app_2_3.dtd > In setups that are behind firewalls with limited access to external > resources, the Atlas server fails to come up without the external dtd > resource. > This can be fixed by hosting dtd resource locally or upgrading the deployment > descriptor. > We can upgrade it to Servlet 2.5 deployment descriptor which is Java EE 5 XML > schema and it does not require external dtd resource for validation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4284) Pruned tables are ignored
Radhika Kundam created ATLAS-4284: - Summary: Pruned tables are ignored Key: ATLAS-4284 URL: https://issues.apache.org/jira/browse/ATLAS-4284 Project: Atlas Issue Type: Bug Reporter: Radhika Kundam Assignee: Radhika Kundam Settings in Atlas Server: atlas.notification.consumer.preprocess.hive_table.prune.pattern=db2.* No config changes for prune/update made in hive. With the above settings , created db2.table1. The table is ignored instead of getting pruned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Review Request 73340: ATLAS-4274: Non matching relation are created via bulk import
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73340/ --- (Updated May 12, 2021, 8 p.m.) Review request for atlas, Ashutosh Mestry and Sarath Subramanian. Bugs: ATLAS-4274 https://issues.apache.org/jira/browse/ATLAS-4274 Repository: atlas Description --- ATLAS-4274: Added code to load some terms from graph DB if needed during glossary import Diffs (updated) - repository/src/main/java/org/apache/atlas/glossary/GlossaryService.java 73217ded3 repository/src/main/java/org/apache/atlas/glossary/GlossaryTermUtils.java 553d3d0a6 Diff: https://reviews.apache.org/r/73340/diff/3/ Changes: https://reviews.apache.org/r/73340/diff/2-3/ Testing --- Manually tested and confirmed its working as expected. org.apache.atlas.glossary.GlossaryServiceTest UTs are passing. Thanks, Sidharth Mishra
[jira] [Updated] (ATLAS-4164) [Atlas: Spooling] Tables created after spooling are created before the spooled tables when there is multiple frequent restart in kafka brokers
[
https://issues.apache.org/jira/browse/ATLAS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4164:
--
Labels: spool (was: )
> [Atlas: Spooling] Tables created after spooling are created before the
> spooled tables when there is multiple frequent restart in kafka brokers
> --
>
> Key: ATLAS-4164
> URL: https://issues.apache.org/jira/browse/ATLAS-4164
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Ashutosh Mestry
>Priority: Major
> Labels: spool
> Fix For: 3.0.0
>
> Attachments: ATLAS-4164-Spooling-Status.patch
>
>
> Scenario:
> * Stop kafka broker
> * Create a few (20) tables save the prefix (abc_table_1, abc_table_2, ...
> abc_table_n)
> * Make sure the data is spooled
> * Start kafka and create a few more tables (xyz_table_1, xyz_table_2, ...
> xyz_table_n)
> * Wait for 5 mins for the tables to reflect in atlas
> In this case we expect all the abc_table_* to be created before xyz_table_1,
> meaning all the spooled tables are created before the tables that are created
> after spooling.
>
> Observation:
> createTime of some spooled tables is greater than the create time of the
> xyz_table_1
>
> Sample data:
> createTime for tables that are spooled:
> {code:java}
> [1613573518284, 1613573531470, 1613573531861, 1613573529446, 1613573543253,
> 1613573525390, 1613573525950, 1613573517796, 1613573518284, 1613573522629,
> 1613573513524, 1613573524856, 1613573518992, 1613573519477, 1613573519947,
> 1613573521737, 1613573514066, 1613573514555, 1613573515065,
> 1613573515605]{code}
> createTime for tables that are created after spooling:
> {code:java}
> [1613573540582, 1613573541300, 1613573551691, 1613573552628, 1613573553356,
> 1613573555478, 1613573556275, 1613573556940, 1613573557763, 1613573558659,
> 1613573560673, 1613573561363, 1613573562310, 1613573563096, 1613573564004,
> 1613573566533, 1613573567602, 1613573568439, 1613573569379, 1613573570202]
> {code}
> We expect all spooled tables to have createTime smaller than the tables
> created after spooling.
> But *1613573543253 (Spooled tabled create time) is greater than 1613573540582
> (table created after spooling)*
> which means, the table created after spooling is created before spooled table
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (ATLAS-4164) [Atlas: Spooling] Tables created after spooling are created before the spooled tables when there is multiple frequent restart in kafka brokers
[
https://issues.apache.org/jira/browse/ATLAS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian reassigned ATLAS-4164:
-
Assignee: Radhika Kundam (was: Ashutosh Mestry)
> [Atlas: Spooling] Tables created after spooling are created before the
> spooled tables when there is multiple frequent restart in kafka brokers
> --
>
> Key: ATLAS-4164
> URL: https://issues.apache.org/jira/browse/ATLAS-4164
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Radhika Kundam
>Priority: Major
> Labels: spool
> Fix For: 3.0.0
>
> Attachments: ATLAS-4164-Spooling-Status.patch
>
>
> Scenario:
> * Stop kafka broker
> * Create a few (20) tables save the prefix (abc_table_1, abc_table_2, ...
> abc_table_n)
> * Make sure the data is spooled
> * Start kafka and create a few more tables (xyz_table_1, xyz_table_2, ...
> xyz_table_n)
> * Wait for 5 mins for the tables to reflect in atlas
> In this case we expect all the abc_table_* to be created before xyz_table_1,
> meaning all the spooled tables are created before the tables that are created
> after spooling.
>
> Observation:
> createTime of some spooled tables is greater than the create time of the
> xyz_table_1
>
> Sample data:
> createTime for tables that are spooled:
> {code:java}
> [1613573518284, 1613573531470, 1613573531861, 1613573529446, 1613573543253,
> 1613573525390, 1613573525950, 1613573517796, 1613573518284, 1613573522629,
> 1613573513524, 1613573524856, 1613573518992, 1613573519477, 1613573519947,
> 1613573521737, 1613573514066, 1613573514555, 1613573515065,
> 1613573515605]{code}
> createTime for tables that are created after spooling:
> {code:java}
> [1613573540582, 1613573541300, 1613573551691, 1613573552628, 1613573553356,
> 1613573555478, 1613573556275, 1613573556940, 1613573557763, 1613573558659,
> 1613573560673, 1613573561363, 1613573562310, 1613573563096, 1613573564004,
> 1613573566533, 1613573567602, 1613573568439, 1613573569379, 1613573570202]
> {code}
> We expect all spooled tables to have createTime smaller than the tables
> created after spooling.
> But *1613573543253 (Spooled tabled create time) is greater than 1613573540582
> (table created after spooling)*
> which means, the table created after spooling is created before spooled table
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4164) [Atlas: Spooling] Tables created after spooling are created before the spooled tables when there is multiple frequent restart in kafka brokers
[
https://issues.apache.org/jira/browse/ATLAS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4164:
--
Affects Version/s: (was: 3.0.0)
> [Atlas: Spooling] Tables created after spooling are created before the
> spooled tables when there is multiple frequent restart in kafka brokers
> --
>
> Key: ATLAS-4164
> URL: https://issues.apache.org/jira/browse/ATLAS-4164
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-4164-Spooling-Status.patch
>
>
> Scenario:
> * Stop kafka broker
> * Create a few (20) tables save the prefix (abc_table_1, abc_table_2, ...
> abc_table_n)
> * Make sure the data is spooled
> * Start kafka and create a few more tables (xyz_table_1, xyz_table_2, ...
> xyz_table_n)
> * Wait for 5 mins for the tables to reflect in atlas
> In this case we expect all the abc_table_* to be created before xyz_table_1,
> meaning all the spooled tables are created before the tables that are created
> after spooling.
>
> Observation:
> createTime of some spooled tables is greater than the create time of the
> xyz_table_1
>
> Sample data:
> createTime for tables that are spooled:
> {code:java}
> [1613573518284, 1613573531470, 1613573531861, 1613573529446, 1613573543253,
> 1613573525390, 1613573525950, 1613573517796, 1613573518284, 1613573522629,
> 1613573513524, 1613573524856, 1613573518992, 1613573519477, 1613573519947,
> 1613573521737, 1613573514066, 1613573514555, 1613573515065,
> 1613573515605]{code}
> createTime for tables that are created after spooling:
> {code:java}
> [1613573540582, 1613573541300, 1613573551691, 1613573552628, 1613573553356,
> 1613573555478, 1613573556275, 1613573556940, 1613573557763, 1613573558659,
> 1613573560673, 1613573561363, 1613573562310, 1613573563096, 1613573564004,
> 1613573566533, 1613573567602, 1613573568439, 1613573569379, 1613573570202]
> {code}
> We expect all spooled tables to have createTime smaller than the tables
> created after spooling.
> But *1613573543253 (Spooled tabled create time) is greater than 1613573540582
> (table created after spooling)*
> which means, the table created after spooling is created before spooled table
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4164) [Atlas: Spooling] Tables created after spooling are created before the spooled tables when there is multiple frequent restart in kafka brokers
[
https://issues.apache.org/jira/browse/ATLAS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4164:
--
Affects Version/s: 3.0.0
2.1.0
> [Atlas: Spooling] Tables created after spooling are created before the
> spooled tables when there is multiple frequent restart in kafka brokers
> --
>
> Key: ATLAS-4164
> URL: https://issues.apache.org/jira/browse/ATLAS-4164
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0, 3.0.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-4164-Spooling-Status.patch
>
>
> Scenario:
> * Stop kafka broker
> * Create a few (20) tables save the prefix (abc_table_1, abc_table_2, ...
> abc_table_n)
> * Make sure the data is spooled
> * Start kafka and create a few more tables (xyz_table_1, xyz_table_2, ...
> xyz_table_n)
> * Wait for 5 mins for the tables to reflect in atlas
> In this case we expect all the abc_table_* to be created before xyz_table_1,
> meaning all the spooled tables are created before the tables that are created
> after spooling.
>
> Observation:
> createTime of some spooled tables is greater than the create time of the
> xyz_table_1
>
> Sample data:
> createTime for tables that are spooled:
> {code:java}
> [1613573518284, 1613573531470, 1613573531861, 1613573529446, 1613573543253,
> 1613573525390, 1613573525950, 1613573517796, 1613573518284, 1613573522629,
> 1613573513524, 1613573524856, 1613573518992, 1613573519477, 1613573519947,
> 1613573521737, 1613573514066, 1613573514555, 1613573515065,
> 1613573515605]{code}
> createTime for tables that are created after spooling:
> {code:java}
> [1613573540582, 1613573541300, 1613573551691, 1613573552628, 1613573553356,
> 1613573555478, 1613573556275, 1613573556940, 1613573557763, 1613573558659,
> 1613573560673, 1613573561363, 1613573562310, 1613573563096, 1613573564004,
> 1613573566533, 1613573567602, 1613573568439, 1613573569379, 1613573570202]
> {code}
> We expect all spooled tables to have createTime smaller than the tables
> created after spooling.
> But *1613573543253 (Spooled tabled create time) is greater than 1613573540582
> (table created after spooling)*
> which means, the table created after spooling is created before spooled table
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4164) [Atlas: Spooling] Tables created after spooling are created before the spooled tables when there is multiple frequent restart in kafka brokers
[
https://issues.apache.org/jira/browse/ATLAS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarath Subramanian updated ATLAS-4164:
--
Fix Version/s: 3.0.0
> [Atlas: Spooling] Tables created after spooling are created before the
> spooled tables when there is multiple frequent restart in kafka brokers
> --
>
> Key: ATLAS-4164
> URL: https://issues.apache.org/jira/browse/ATLAS-4164
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 2.1.0
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4164-Spooling-Status.patch
>
>
> Scenario:
> * Stop kafka broker
> * Create a few (20) tables save the prefix (abc_table_1, abc_table_2, ...
> abc_table_n)
> * Make sure the data is spooled
> * Start kafka and create a few more tables (xyz_table_1, xyz_table_2, ...
> xyz_table_n)
> * Wait for 5 mins for the tables to reflect in atlas
> In this case we expect all the abc_table_* to be created before xyz_table_1,
> meaning all the spooled tables are created before the tables that are created
> after spooling.
>
> Observation:
> createTime of some spooled tables is greater than the create time of the
> xyz_table_1
>
> Sample data:
> createTime for tables that are spooled:
> {code:java}
> [1613573518284, 1613573531470, 1613573531861, 1613573529446, 1613573543253,
> 1613573525390, 1613573525950, 1613573517796, 1613573518284, 1613573522629,
> 1613573513524, 1613573524856, 1613573518992, 1613573519477, 1613573519947,
> 1613573521737, 1613573514066, 1613573514555, 1613573515065,
> 1613573515605]{code}
> createTime for tables that are created after spooling:
> {code:java}
> [1613573540582, 1613573541300, 1613573551691, 1613573552628, 1613573553356,
> 1613573555478, 1613573556275, 1613573556940, 1613573557763, 1613573558659,
> 1613573560673, 1613573561363, 1613573562310, 1613573563096, 1613573564004,
> 1613573566533, 1613573567602, 1613573568439, 1613573569379, 1613573570202]
> {code}
> We expect all spooled tables to have createTime smaller than the tables
> created after spooling.
> But *1613573543253 (Spooled tabled create time) is greater than 1613573540582
> (table created after spooling)*
> which means, the table created after spooling is created before spooled table
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4164) [Atlas: Spooling] Tables created after spooling are created before the spooled tables when there is multiple frequent restart in kafka brokers
[
https://issues.apache.org/jira/browse/ATLAS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343366#comment-17343366
]
ASF subversion and git services commented on ATLAS-4164:
Commit 4100684fa3f63cb2a6267ab24051002ce38de017 in atlas's branch
refs/heads/master from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4100684 ]
ATLAS-4164: [Atlas: Spooling] Tables created after spooling are created before
the spooled tables when there is multiple frequent restart in kafka brokers
Signed-off-by: Sarath Subramanian
> [Atlas: Spooling] Tables created after spooling are created before the
> spooled tables when there is multiple frequent restart in kafka brokers
> --
>
> Key: ATLAS-4164
> URL: https://issues.apache.org/jira/browse/ATLAS-4164
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Dharshana M Krishnamoorthy
>Assignee: Ashutosh Mestry
>Priority: Major
> Attachments: ATLAS-4164-Spooling-Status.patch
>
>
> Scenario:
> * Stop kafka broker
> * Create a few (20) tables save the prefix (abc_table_1, abc_table_2, ...
> abc_table_n)
> * Make sure the data is spooled
> * Start kafka and create a few more tables (xyz_table_1, xyz_table_2, ...
> xyz_table_n)
> * Wait for 5 mins for the tables to reflect in atlas
> In this case we expect all the abc_table_* to be created before xyz_table_1,
> meaning all the spooled tables are created before the tables that are created
> after spooling.
>
> Observation:
> createTime of some spooled tables is greater than the create time of the
> xyz_table_1
>
> Sample data:
> createTime for tables that are spooled:
> {code:java}
> [1613573518284, 1613573531470, 1613573531861, 1613573529446, 1613573543253,
> 1613573525390, 1613573525950, 1613573517796, 1613573518284, 1613573522629,
> 1613573513524, 1613573524856, 1613573518992, 1613573519477, 1613573519947,
> 1613573521737, 1613573514066, 1613573514555, 1613573515065,
> 1613573515605]{code}
> createTime for tables that are created after spooling:
> {code:java}
> [1613573540582, 1613573541300, 1613573551691, 1613573552628, 1613573553356,
> 1613573555478, 1613573556275, 1613573556940, 1613573557763, 1613573558659,
> 1613573560673, 1613573561363, 1613573562310, 1613573563096, 1613573564004,
> 1613573566533, 1613573567602, 1613573568439, 1613573569379, 1613573570202]
> {code}
> We expect all spooled tables to have createTime smaller than the tables
> created after spooling.
> But *1613573543253 (Spooled tabled create time) is greater than 1613573540582
> (table created after spooling)*
> which means, the table created after spooling is created before spooled table
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (ATLAS-4282) Atlas Authentication to database Cassandra
[
https://issues.apache.org/jira/browse/ATLAS-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
romain resolved ATLAS-4282.
---
Resolution: Done
> Atlas Authentication to database Cassandra
> --
>
> Key: ATLAS-4282
> URL: https://issues.apache.org/jira/browse/ATLAS-4282
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 2.1.0
> Environment: Cassandra 3.11
> Solr 8.8.2
> zookeeper 3.7.0
>Reporter: romain
>Priority: Major
> Labels: authentication, cassandra
> Attachments: config_file.txt, issue.txt
>
>
> On documentation their is no details for how setup authentication for the
> database
> just a ${graph.storage.properties} in the github [github
> application_file|https://github.com/apache/atlas/blob/master/distro/src/conf/atlas-application.properties]
> , if the documentaion can be update cause the only solution i've found is
> deploy a database without authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (ATLAS-4282) Atlas Authentication to database Cassandra
[
https://issues.apache.org/jira/browse/ATLAS-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343293#comment-17343293
]
romain edited comment on ATLAS-4282 at 5/12/21, 3:00 PM:
-
solved with the use of
{color:#ce9178}atlas.graph.storage.username={color}
{color:#ce9178}atlas.graph.storage.password={color}
{color:#172b4d}in the .properties file
{color}
{color:#172b4d}https://docs.janusgraph.org/master/configs/configuration-reference/#indexxsolr{color}
was (Author: romainp):
solved with the use of
{color:#ce9178}atlas.graph.storage.username={color}
{color:#ce9178}atlas.graph.storage.password={color}
{color:#172b4d}in the .properties file{color}
> Atlas Authentication to database Cassandra
> --
>
> Key: ATLAS-4282
> URL: https://issues.apache.org/jira/browse/ATLAS-4282
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 2.1.0
> Environment: Cassandra 3.11
> Solr 8.8.2
> zookeeper 3.7.0
>Reporter: romain
>Priority: Major
> Labels: authentication, cassandra
> Attachments: config_file.txt, issue.txt
>
>
> On documentation their is no details for how setup authentication for the
> database
> just a ${graph.storage.properties} in the github [github
> application_file|https://github.com/apache/atlas/blob/master/distro/src/conf/atlas-application.properties]
> , if the documentaion can be update cause the only solution i've found is
> deploy a database without authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ATLAS-4282) Atlas Authentication to database Cassandra
[
https://issues.apache.org/jira/browse/ATLAS-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343293#comment-17343293
]
romain commented on ATLAS-4282:
---
solved with the use of
{color:#ce9178}atlas.graph.storage.username={color}
{color:#ce9178}atlas.graph.storage.password={color}
{color:#172b4d}in the .properties file{color}
> Atlas Authentication to database Cassandra
> --
>
> Key: ATLAS-4282
> URL: https://issues.apache.org/jira/browse/ATLAS-4282
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 2.1.0
> Environment: Cassandra 3.11
> Solr 8.8.2
> zookeeper 3.7.0
>Reporter: romain
>Priority: Major
> Labels: authentication, cassandra
> Attachments: config_file.txt, issue.txt
>
>
> On documentation their is no details for how setup authentication for the
> database
> just a ${graph.storage.properties} in the github [github
> application_file|https://github.com/apache/atlas/blob/master/distro/src/conf/atlas-application.properties]
> , if the documentaion can be update cause the only solution i've found is
> deploy a database without authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4283) UI: Description cannot be made blank for classification
Rahul Kurup created ATLAS-4283: -- Summary: UI: Description cannot be made blank for classification Key: ATLAS-4283 URL: https://issues.apache.org/jira/browse/ATLAS-4283 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup If there is an existing description for a classification, and if the user attempts to update it to blank, he will not be able to do so. The API response for when the user inputs a blank value shows that the updated value for the description is the same as the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4282) Atlas Authentication to database Cassandra
[
https://issues.apache.org/jira/browse/ATLAS-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
romain updated ATLAS-4282:
--
Affects Version/s: 2.1.0
> Atlas Authentication to database Cassandra
> --
>
> Key: ATLAS-4282
> URL: https://issues.apache.org/jira/browse/ATLAS-4282
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 2.1.0
> Environment: Cassandra 3.11
> Solr 8.8.2
> zookeeper 3.7.0
>Reporter: romain
>Priority: Major
> Labels: authentication, cassandra
> Attachments: config_file.txt, issue.txt
>
>
> On documentation their is no details for how setup authentication for the
> database
> just a ${graph.storage.properties} in the github [github
> application_file|https://github.com/apache/atlas/blob/master/distro/src/conf/atlas-application.properties]
> , if the documentaion can be update cause the only solution i've found is
> deploy a database without authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ATLAS-4282) Atlas Authentication to database Cassandra
romain created ATLAS-4282:
-
Summary: Atlas Authentication to database Cassandra
Key: ATLAS-4282
URL: https://issues.apache.org/jira/browse/ATLAS-4282
Project: Atlas
Issue Type: Improvement
Environment: Cassandra 3.11
Solr 8.8.2
zookeeper 3.7.0
Reporter: romain
Attachments: config_file.txt, issue.txt
On documentation their is no details for how setup authentication for the
database
just a ${graph.storage.properties} in the github [github
application_file|https://github.com/apache/atlas/blob/master/distro/src/conf/atlas-application.properties]
, if the documentaion can be update cause the only solution i've found is
deploy a database without authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4280: --- Component/s: atlas-webui > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Labels: Atlas-UI, classification > Attachments: > 0001-ATLAS-4280-UI-Save-button-is-enabled-when-Classifica.patch > > > Previously the Save button in the popup box for classification attribute > would not show as enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar reassigned ATLAS-4280: -- Attachment: 0001-ATLAS-4280-UI-Save-button-is-enabled-when-Classifica.patch Assignee: Prasad P. Pawar Labels: Atlas-UI classification (was: ) Hi, this fix is provided in the uploaded patch. > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Assignee: Prasad P. Pawar >Priority: Minor > Labels: Atlas-UI, classification > Attachments: > 0001-ATLAS-4280-UI-Save-button-is-enabled-when-Classifica.patch > > > Previously the Save button in the popup box for classification attribute > would not show as enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4281) Atlas UI: Tasks tab refresh button is seen on other tabs of entity detail page.
Prasad P. Pawar created ATLAS-4281: -- Summary: Atlas UI: Tasks tab refresh button is seen on other tabs of entity detail page. Key: ATLAS-4281 URL: https://issues.apache.org/jira/browse/ATLAS-4281 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar The refresh button of Tasks tab is seen at the bottom of Properties tab, Relationships tab, Classification tabs, Audit tab & schema tabs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4280: --- Description: Previously the Save button in the popup box for classification attribute would not show as enabled if the content of the description field is only updated with the original value of the description field. But now it is showing as enabled when the value is updated with the original value. (was: Previously the Save button in the popup box for classification attribute would not show us enabled if the content of the description field is only updated with the original value of the description field. But now it is showing as enabled when the value is updated with the original value.) > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > > Previously the Save button in the popup box for classification attribute > would not show as enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (ATLAS-3619) Allow to create a namespace typedef without specifying any "applicableEntityTypes"
[ https://issues.apache.org/jira/browse/ATLAS-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-3619. Resolution: Fixed > Allow to create a namespace typedef without specifying any > "applicableEntityTypes" > -- > > Key: ATLAS-3619 > URL: https://issues.apache.org/jira/browse/ATLAS-3619 > Project: Atlas > Issue Type: Bug >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-4280) UI: Save button is enabled when Classification description is updated with original value.
[ https://issues.apache.org/jira/browse/ATLAS-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Kurup updated ATLAS-4280: --- Summary: UI: Save button is enabled when Classification description is updated with original value. (was: Save button is enabled when Classification description is updated with original value.) > UI: Save button is enabled when Classification description is updated with > original value. > -- > > Key: ATLAS-4280 > URL: https://issues.apache.org/jira/browse/ATLAS-4280 > Project: Atlas > Issue Type: Bug >Reporter: Rahul Kurup >Priority: Minor > > Previously the Save button in the popup box for classification attribute > would not show us enabled if the content of the description field is only > updated with the original value of the description field. But now it is > showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-4280) Save button is enabled when Classification description is updated with original value.
Rahul Kurup created ATLAS-4280: -- Summary: Save button is enabled when Classification description is updated with original value. Key: ATLAS-4280 URL: https://issues.apache.org/jira/browse/ATLAS-4280 Project: Atlas Issue Type: Bug Reporter: Rahul Kurup Previously the Save button in the popup box for classification attribute would not show us enabled if the content of the description field is only updated with the original value of the description field. But now it is showing as enabled when the value is updated with the original value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
