[jira] [Assigned] (ATLAS-4712) atlas-hive image shows "No such file or directory error"
[
https://issues.apache.org/jira/browse/ATLAS-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj reassigned ATLAS-4712:
---
Assignee: Madhan Neethiraj (was: Snehal Ambavkar)
> atlas-hive image shows "No such file or directory error"
> -
>
> Key: ATLAS-4712
> URL: https://issues.apache.org/jira/browse/ATLAS-4712
> Project: Atlas
> Issue Type: Bug
>Reporter: Snehal Ambavkar
>Assignee: Madhan Neethiraj
>Priority: Minor
> Fix For: 3.0.0, 2.3.0
>
> Attachments: ATLAS-4712.patch
>
>
> Running docker-compose
> {code:java}
> docker-compose -f docker-compose.atlas-base.yml -f docker-compose.atlas.yml
> -f docker-compose.atlas-hadoop.yml -f docker-compose.atlas-hbase.yml -f
> docker-compose.atlas-kafka.yml -f docker-compose.atlas-hive.yml up -d
> {code}
> shows with:
> {code:java}
> /home/atlas/scripts/atlas-hive-setup.sh: line 44: cd:
> /opt/atlas/atlas-hive-plugin: No such file or directory
> /home/atlas/scripts/atlas-hive-setup.sh: line 45: ./enable-hive-plugin.sh: No
> such file or directory {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-3498) Update basic-search to enable search using labels
[ https://issues.apache.org/jira/browse/ATLAS-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3498: Fix Version/s: 3.0.0 (was: 2.3.0) > Update basic-search to enable search using labels > - > > Key: ATLAS-3498 > URL: https://issues.apache.org/jira/browse/ATLAS-3498 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 3.0.0 > > > Update basic-search to enable search using labels -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-3501) Update guava version to 28.0-jre
[ https://issues.apache.org/jira/browse/ATLAS-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3501: Fix Version/s: 3.0.0 (was: 2.3.0) > Update guava version to 28.0-jre > > > Key: ATLAS-3501 > URL: https://issues.apache.org/jira/browse/ATLAS-3501 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 2.0.0 >Reporter: Aadarsh Jajodia >Assignee: Aadarsh Jajodia >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-ATLAS-3501-Update-guava-version-to-28.0-jre.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-3610) Enable logging to multiple targets (logdir, stdout)
[ https://issues.apache.org/jira/browse/ATLAS-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3610: Fix Version/s: (was: 2.3.0) > Enable logging to multiple targets (logdir, stdout) > --- > > Key: ATLAS-3610 > URL: https://issues.apache.org/jira/browse/ATLAS-3610 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Mariusz Górski >Priority: Minor > Fix For: 3.0.0 > > Attachments: ATLAS-3610-1.patch, ATLAS-3610-2.patch, > ATLAS-3610-3.patch, ATLAS-3610.patch > > Time Spent: 50m > Remaining Estimate: 0h > > *Problem description* > When starting Atlas, Python scripts are invoked to spawn all necessary > processes. This is achieved with the use of _subprocess.Popen()_ in > _runProcess()_ function of _atlas_config.py_ script. While doing that, stdout > is being redirected to log files, which (for java processes) can override > log4j configuration (if configured with stdout handler). This creates > situation when log4j configuration cannot be relied upon and prevents logging > to stdout. > *Proposed solution* > * Add possibility to log to stdout by using multiple stdout/stderr handlers > * Adjust _runProcess()_ function from _atlas_config.py_ script (and all > functions relying on it) to provide _logconsole_ kwarg which will add > additional handler to Popen stdout/stderr redirection > * Add _ENABLE_LOGGING_TO_CONSOLE_ env variable (defaulting to _False_) for > backwards compatibility. > * Adjust _atlas_start.py_ script to make use of _ENABLE_LOGGING_TO_CONSOLE_ > and provide it in functions invoking atlas/solr/elasticsearch/zookeeper > *Predicted Benefits* > This improvement would bring the benefit of enabling logging to stdout (which > is supressed for now even if configured in spawned components), which could > be very useful when running Atlas in docker container or in Kubernetes/OC, > where some logging scraping is present. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-3890) Enhancement for all BulkAPIs.
[
https://issues.apache.org/jira/browse/ATLAS-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-3890:
Fix Version/s: 3.0.0
(was: 2.3.0)
> Enhancement for all BulkAPIs.
> -
>
> Key: ATLAS-3890
> URL: https://issues.apache.org/jira/browse/ATLAS-3890
> Project: Atlas
> Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: chaitali borole
>Assignee: chaitali borole
>Priority: Major
> Labels: api-change
> Fix For: 3.0.0
>
>
> According to below linked Atlas Jira two Bulk Apis are enhanced to return
> authorised entities or modify them when some of then entity types are blocked
> by policies in Ranger for access to user.Hence we are improving the other
> bulk Apis too.
> Previously user only used to get 403 error if he tries to access or modify
> entities which comprised of both authorised as well as unauthorised typenames.
> DELETE /bulk - EntityREST.deleteByGuids()
> GET /bulk/uniqueAttribute/type/\{typeName} -
> EntityREST.getEntitiesByUniqueAttributes()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (ATLAS-4679) Indexing of deleted relationship edges prolongs entity update time
[ https://issues.apache.org/jira/browse/ATLAS-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-4679. - Resolution: Fixed > Indexing of deleted relationship edges prolongs entity update time > -- > > Key: ATLAS-4679 > URL: https://issues.apache.org/jira/browse/ATLAS-4679 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: VINAYAK MARRAIYA >Assignee: Sheetal Shah >Priority: Major > Fix For: 3.0.0, 2.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74195: ATLAS-3403 : Term assigned to historical entity is not visible in Search results page.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74195/
---
(Updated Nov. 17, 2022, 1:47 p.m.)
Review request for atlas, Jayendra Parab and Pinal Shah.
Bugs: ATLAS-3403
https://issues.apache.org/jira/browse/ATLAS-3403
Repository: atlas
Description
---
Let us consider that a classification and a term has been assigned to an
entity.
If that entity is deleted, and then when the "Show Historical Entities" filter
is enabled on the search results page for that entity, the classification is
displayed but not the term.
This patch handles above issue
Diffs (updated)
-
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
0ed418330
repository/src/test/java/org/apache/atlas/glossary/GlossaryServiceTest.java
27717c313
Diff: https://reviews.apache.org/r/74195/diff/3/
Changes: https://reviews.apache.org/r/74195/diff/2-3/
Testing
---
mvn clean install
Entities ,classification,terms,glossaries getting created successfully
PC successful
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1284/console
Created an Entity of type hdfs_path as "abc" added classification "class1" and
assigned a term as well "term1"
then deleted the entity when we search this entity using
http://localhost:21000/api/atlas/v2/search/basic
without the fix we cant see "term1" in response under "meanings" tab because
there is a check in the code where if edge is deleted we then term will not be
assigned to the deleted entity hence we couldnt see it under "show historical
data"
Below json for output after fixing issue we can see term getting added in
MeaningNames and meanings:
http://localhost:21000/api/atlas/v2/search/basic
{"queryType":"BASIC","searchParameters":{"typeName":"hdfs_path","excludeDeletedEntities":false,"includeClassificationAttributes":true,"includeSubTypes":true,"includeSubClassifications":true,"excludeHeaderAttributes":false,"limit":25,"offset":0,"attributes":[]},"entities":[{"typeName":"hdfs_path","attributes":{"owner":"","createTime":166784580,"qualifiedName":"abc","name":"abc","description":""},"guid":"22f365a3-5d7c-49d0-b2dc-324adf77d3fe","status":"DELETED","displayText":"abc","classificationNames":["class1"],"classifications":[{"typeName":"class1","entityGuid":"22f365a3-5d7c-49d0-b2dc-324adf77d3fe","entityStatus":"DELETED","propagate":true,"validityPeriods":[],"removePropagationsOnEntityDelete":false}],"meaningNames":["term1"],"meanings":[{"termGuid":"c983b9b9-5b0a-409b-9a30-c0328cd1b3ad","relationGuid":"29ddea1a-adbf-4e48-9c85-72b8a97e10ac","displayText":"term1","confidence":0,"qualifiedName":"term1@gloss1"}],"isIncomplete":false,"labels":[]}],"approximateCount":1}
Thanks,
chaitali
Re: Review Request 74195: ATLAS-3403 : Term assigned to historical entity is not visible in Search results page.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74195/
---
(Updated Nov. 17, 2022, 11:43 a.m.)
Review request for atlas, Jayendra Parab and Pinal Shah.
Bugs: ATLAS-3403
https://issues.apache.org/jira/browse/ATLAS-3403
Repository: atlas
Description
---
Let us consider that a classification and a term has been assigned to an
entity.
If that entity is deleted, and then when the "Show Historical Entities" filter
is enabled on the search results page for that entity, the classification is
displayed but not the term.
This patch handles above issue
Diffs (updated)
-
repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphRetriever.java
0ed418330
repository/src/test/java/org/apache/atlas/glossary/GlossaryServiceTest.java
27717c313
Diff: https://reviews.apache.org/r/74195/diff/2/
Changes: https://reviews.apache.org/r/74195/diff/1-2/
Testing
---
mvn clean install
Entities ,classification,terms,glossaries getting created successfully
PC successful
https://ci-builds.apache.org/job/Atlas/job/PreCommit-ATLAS-Build-Test/1284/console
Created an Entity of type hdfs_path as "abc" added classification "class1" and
assigned a term as well "term1"
then deleted the entity when we search this entity using
http://localhost:21000/api/atlas/v2/search/basic
without the fix we cant see "term1" in response under "meanings" tab because
there is a check in the code where if edge is deleted we then term will not be
assigned to the deleted entity hence we couldnt see it under "show historical
data"
Below json for output after fixing issue we can see term getting added in
MeaningNames and meanings:
http://localhost:21000/api/atlas/v2/search/basic
{"queryType":"BASIC","searchParameters":{"typeName":"hdfs_path","excludeDeletedEntities":false,"includeClassificationAttributes":true,"includeSubTypes":true,"includeSubClassifications":true,"excludeHeaderAttributes":false,"limit":25,"offset":0,"attributes":[]},"entities":[{"typeName":"hdfs_path","attributes":{"owner":"","createTime":166784580,"qualifiedName":"abc","name":"abc","description":""},"guid":"22f365a3-5d7c-49d0-b2dc-324adf77d3fe","status":"DELETED","displayText":"abc","classificationNames":["class1"],"classifications":[{"typeName":"class1","entityGuid":"22f365a3-5d7c-49d0-b2dc-324adf77d3fe","entityStatus":"DELETED","propagate":true,"validityPeriods":[],"removePropagationsOnEntityDelete":false}],"meaningNames":["term1"],"meanings":[{"termGuid":"c983b9b9-5b0a-409b-9a30-c0328cd1b3ad","relationGuid":"29ddea1a-adbf-4e48-9c85-72b8a97e10ac","displayText":"term1","confidence":0,"qualifiedName":"term1@gloss1"}],"isIncomplete":false,"labels":[]}],"approximateCount":1}
Thanks,
chaitali
[jira] [Commented] (ATLAS-4699) Change pom version from 2.3.0-SNAPSHOT to 2.3.0
[ https://issues.apache.org/jira/browse/ATLAS-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635273#comment-17635273 ] ASF subversion and git services commented on ATLAS-4699: Commit 518e6eb5e54907ad8392d26be7929c08971ef011 in atlas's branch refs/heads/branch-2.0 from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=518e6eb5e ] ATLAS-4699: updated version in pom.xml from 2.3.0-SNAPSHOT to 2.3.0 > Change pom version from 2.3.0-SNAPSHOT to 2.3.0 > --- > > Key: ATLAS-4699 > URL: https://issues.apache.org/jira/browse/ATLAS-4699 > Project: Atlas > Issue Type: Sub-task >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.3.0 > > Attachments: ATLAS-4699.patch > > > Update pom version from 2.3.0-SNAPSHOT to 2.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74205: ATLAS-4699: updated version in pom.xml from 2.3.0-SNAPSHOT to 2.3.0
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74205/#review224882 --- Ship it! Ship It! - Mandar Ambawane On Nov. 17, 2022, 8:52 a.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74205/ > --- > > (Updated Nov. 17, 2022, 8:52 a.m.) > > > Review request for atlas, Ashutosh Mestry, Jayendra Parab, Mandar Ambawane, > Nikhil Bonte, Nixon Rodrigues, Pinal Shah, Radhika Kundam, Sarath > Subramanian, and Sidharth Mishra. > > > Bugs: ATLAS-4699 > https://issues.apache.org/jira/browse/ATLAS-4699 > > > Repository: atlas > > > Description > --- > > updated Atlas version from 2.3.0-SNAPSHOT to 2.3.0 > > > Diffs > - > > addons/falcon-bridge-shim/pom.xml 981e76418 > addons/falcon-bridge/pom.xml 8e25111d4 > addons/hbase-bridge-shim/pom.xml ef3c1bad9 > addons/hbase-bridge/pom.xml 5a0f62fb3 > addons/hbase-testing-util/pom.xml 947ca477f > addons/hdfs-model/pom.xml 226b0d49b > addons/hive-bridge-shim/pom.xml cb4dbb3ae > addons/hive-bridge/pom.xml 80a2252c5 > addons/impala-bridge-shim/pom.xml 247dc10ae > addons/impala-bridge/pom.xml cacdf4a98 > addons/impala-hook-api/pom.xml 8b61994f7 > addons/kafka-bridge/pom.xml 31f5d5b3a > addons/sqoop-bridge-shim/pom.xml 4ba77d521 > addons/sqoop-bridge/pom.xml 62e2eee00 > addons/storm-bridge-shim/pom.xml 510718c8d > addons/storm-bridge/pom.xml a5017e0b2 > atlas-examples/pom.xml 12cd8c401 > atlas-examples/sample-app/pom.xml e2eb42f54 > authorization/pom.xml 177f2dde3 > build-tools/pom.xml 01c573258 > client/client-v1/pom.xml fc80a4294 > client/client-v2/pom.xml deb991001 > client/common/pom.xml e9959bf47 > client/pom.xml 5057e4c02 > common/pom.xml 554ab67d2 > dashboardv2/pom.xml 965e5856e > dashboardv3/pom.xml 2e1729988 > dev-support/atlas-docker/.env ca597ac04 > distro/pom.xml a892736de > docs/pom.xml 9b99d5caf > graphdb/api/pom.xml 741cf8d89 > graphdb/common/pom.xml 0e96d46f9 > graphdb/graphdb-impls/pom.xml 897a48dc8 > graphdb/janus-hbase2/pom.xml 4da5ae8e4 > graphdb/janus/pom.xml 75eed0f16 > graphdb/pom.xml 0fde3510a > intg/pom.xml 3a34983a5 > notification/pom.xml e8abd453e > plugin-classloader/pom.xml 2057d3554 > pom.xml 4cc2201c1 > repository/pom.xml eeb7af9de > server-api/pom.xml 0c5e66ec2 > test-tools/pom.xml 6622512fe > tools/atlas-index-repair/pom.xml 9298f91ba > tools/classification-updater/pom.xml 04e766bd2 > webapp/pom.xml 30c7b416b > > > Diff: https://reviews.apache.org/r/74205/diff/1/ > > > Testing > --- > > verified that Atlas builds successfully > > > Thanks, > > Madhan Neethiraj > >
Review Request 74205: ATLAS-4699: updated version in pom.xml from 2.3.0-SNAPSHOT to 2.3.0
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74205/ --- Review request for atlas, Ashutosh Mestry, Jayendra Parab, Mandar Ambawane, Nikhil Bonte, Nixon Rodrigues, Pinal Shah, Radhika Kundam, Sarath Subramanian, and Sidharth Mishra. Bugs: ATLAS-4699 https://issues.apache.org/jira/browse/ATLAS-4699 Repository: atlas Description --- updated Atlas version from 2.3.0-SNAPSHOT to 2.3.0 Diffs - addons/falcon-bridge-shim/pom.xml 981e76418 addons/falcon-bridge/pom.xml 8e25111d4 addons/hbase-bridge-shim/pom.xml ef3c1bad9 addons/hbase-bridge/pom.xml 5a0f62fb3 addons/hbase-testing-util/pom.xml 947ca477f addons/hdfs-model/pom.xml 226b0d49b addons/hive-bridge-shim/pom.xml cb4dbb3ae addons/hive-bridge/pom.xml 80a2252c5 addons/impala-bridge-shim/pom.xml 247dc10ae addons/impala-bridge/pom.xml cacdf4a98 addons/impala-hook-api/pom.xml 8b61994f7 addons/kafka-bridge/pom.xml 31f5d5b3a addons/sqoop-bridge-shim/pom.xml 4ba77d521 addons/sqoop-bridge/pom.xml 62e2eee00 addons/storm-bridge-shim/pom.xml 510718c8d addons/storm-bridge/pom.xml a5017e0b2 atlas-examples/pom.xml 12cd8c401 atlas-examples/sample-app/pom.xml e2eb42f54 authorization/pom.xml 177f2dde3 build-tools/pom.xml 01c573258 client/client-v1/pom.xml fc80a4294 client/client-v2/pom.xml deb991001 client/common/pom.xml e9959bf47 client/pom.xml 5057e4c02 common/pom.xml 554ab67d2 dashboardv2/pom.xml 965e5856e dashboardv3/pom.xml 2e1729988 dev-support/atlas-docker/.env ca597ac04 distro/pom.xml a892736de docs/pom.xml 9b99d5caf graphdb/api/pom.xml 741cf8d89 graphdb/common/pom.xml 0e96d46f9 graphdb/graphdb-impls/pom.xml 897a48dc8 graphdb/janus-hbase2/pom.xml 4da5ae8e4 graphdb/janus/pom.xml 75eed0f16 graphdb/pom.xml 0fde3510a intg/pom.xml 3a34983a5 notification/pom.xml e8abd453e plugin-classloader/pom.xml 2057d3554 pom.xml 4cc2201c1 repository/pom.xml eeb7af9de server-api/pom.xml 0c5e66ec2 test-tools/pom.xml 6622512fe tools/atlas-index-repair/pom.xml 9298f91ba tools/classification-updater/pom.xml 04e766bd2 webapp/pom.xml 30c7b416b Diff: https://reviews.apache.org/r/74205/diff/1/ Testing --- verified that Atlas builds successfully Thanks, Madhan Neethiraj
[jira] [Commented] (ATLAS-4707) update UI component version for scss-tokenizer, node-sass and loader-utils
[ https://issues.apache.org/jira/browse/ATLAS-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635214#comment-17635214 ] ASF subversion and git services commented on ATLAS-4707: Commit 3cfa8787acd6ea6c84f77df155888d08bb528fad in atlas's branch refs/heads/branch-2.0 from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=3cfa8787a ] ATLAS-4707: updated loader-utils version from 1.4.1 to 1.4.2 - #3 Signed-off-by: Madhan Neethiraj (cherry picked from commit d9a2c91aae5c6f0273da12b753a9c66b43c5e73e) > update UI component version for scss-tokenizer, node-sass and loader-utils > -- > > Key: ATLAS-4707 > URL: https://issues.apache.org/jira/browse/ATLAS-4707 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > This Jira tracks version updates in following pull requests: > - [pull request #202|https://github.com/apache/atlas/pull/202] > - [pull request #201|https://github.com/apache/atlas/pull/201] > - [pull request #205|https://github.com/apache/atlas/pull/205] > - [pull request #206|https://github.com/apache/atlas/pull/206] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [atlas] dependabot[bot] closed pull request #208: Bump loader-utils from 1.4.1 to 1.4.2 in /dashboardv2/public/js/external_lib/atlas-lineage
dependabot[bot] closed pull request #208: Bump loader-utils from 1.4.1 to 1.4.2 in /dashboardv2/public/js/external_lib/atlas-lineage URL: https://github.com/apache/atlas/pull/208 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [atlas] dependabot[bot] commented on pull request #208: Bump loader-utils from 1.4.1 to 1.4.2 in /dashboardv2/public/js/external_lib/atlas-lineage
dependabot[bot] commented on PR #208: URL: https://github.com/apache/atlas/pull/208#issuecomment-1318288770 Looks like loader-utils is up-to-date now, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (ATLAS-4707) update UI component version for scss-tokenizer, node-sass and loader-utils
[ https://issues.apache.org/jira/browse/ATLAS-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635213#comment-17635213 ] ASF subversion and git services commented on ATLAS-4707: Commit d9a2c91aae5c6f0273da12b753a9c66b43c5e73e in atlas's branch refs/heads/master from dependabot[bot] [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d9a2c91aa ] ATLAS-4707: updated loader-utils version from 1.4.1 to 1.4.2 - #3 Signed-off-by: Madhan Neethiraj > update UI component version for scss-tokenizer, node-sass and loader-utils > -- > > Key: ATLAS-4707 > URL: https://issues.apache.org/jira/browse/ATLAS-4707 > Project: Atlas > Issue Type: Improvement > Components: atlas-webui >Reporter: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > This Jira tracks version updates in following pull requests: > - [pull request #202|https://github.com/apache/atlas/pull/202] > - [pull request #201|https://github.com/apache/atlas/pull/201] > - [pull request #205|https://github.com/apache/atlas/pull/205] > - [pull request #206|https://github.com/apache/atlas/pull/206] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [atlas] dependabot[bot] closed pull request #207: Bump loader-utils from 1.4.1 to 1.4.2 in /dashboardv3/public/js/external_lib/atlas-lineage
dependabot[bot] closed pull request #207: Bump loader-utils from 1.4.1 to 1.4.2 in /dashboardv3/public/js/external_lib/atlas-lineage URL: https://github.com/apache/atlas/pull/207 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [atlas] dependabot[bot] commented on pull request #207: Bump loader-utils from 1.4.1 to 1.4.2 in /dashboardv3/public/js/external_lib/atlas-lineage
dependabot[bot] commented on PR #207: URL: https://github.com/apache/atlas/pull/207#issuecomment-1318288445 Looks like loader-utils is up-to-date now, so this is no longer needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [atlas] dependabot[bot] opened a new pull request, #207: Bump loader-utils from 1.4.1 to 1.4.2 in /dashboardv3/public/js/external_lib/atlas-lineage
dependabot[bot] opened a new pull request, #207: URL: https://github.com/apache/atlas/pull/207 Bumps [loader-utils](https://github.com/webpack/loader-utils) from 1.4.1 to 1.4.2. Release notes Sourced from https://github.com/webpack/loader-utils/releases;>loader-utils's releases. v1.4.2 https://github.com/webpack/loader-utils/compare/v1.4.1...v1.4.2;>1.4.2 (2022-11-11) Bug Fixes ReDoS problem (https://github-redirect.dependabot.com/webpack/loader-utils/issues/226;>#226) (https://github.com/webpack/loader-utils/commit/17cbf8fa8989c1cb45bdd2997aa524729475f1fa;>17cbf8f) Changelog Sourced from https://github.com/webpack/loader-utils/blob/v1.4.2/CHANGELOG.md;>loader-utils's changelog. https://github.com/webpack/loader-utils/compare/v1.4.1...v1.4.2;>1.4.2 (2022-11-11) Bug Fixes ReDoS problem (https://github-redirect.dependabot.com/webpack/loader-utils/issues/226;>#226) (https://github.com/webpack/loader-utils/commit/17cbf8fa8989c1cb45bdd2997aa524729475f1fa;>17cbf8f) Commits https://github.com/webpack/loader-utils/commit/331ad5067d9a1a7b8d646692e6959639969210d1;>331ad50 chore(release): 1.4.2 https://github.com/webpack/loader-utils/commit/17cbf8fa8989c1cb45bdd2997aa524729475f1fa;>17cbf8f fix: ReDoS problem (https://github-redirect.dependabot.com/webpack/loader-utils/issues/226;>#226) See full diff in https://github.com/webpack/loader-utils/compare/v1.4.1...v1.4.2;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/atlas/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (ATLAS-4713) docker setup - update component versions
[ https://issues.apache.org/jira/browse/ATLAS-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635198#comment-17635198 ] ASF subversion and git services commented on ATLAS-4713: Commit 4853487d9aa02a7121e4a01b39b6793819059aac in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4853487d9 ] ATLAS-4713: docker setup updates to be in sync with component versions in project pom.xml (cherry picked from commit 887ef24c5069c91fd1fb118d63c8ebca7f2978d5) > docker setup - update component versions > > > Key: ATLAS-4713 > URL: https://issues.apache.org/jira/browse/ATLAS-4713 > Project: Atlas > Issue Type: Bug > Components: atlas-docker >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.3.0 > > Attachments: ATLAS-4713.patch > > > Docker setup needs updates to be in sync with component versions in project > pom.xml file. For example: > * ATLAS_VERSION=2.2.0 should be 2.3.0-SNAPSHOT > * KAFKA_VERSION=2.5.0 should be 2.8.1 > * HIVE_HADOOP_VERSION=3.1.0 should be 3.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [atlas] dependabot[bot] opened a new pull request, #208: Bump loader-utils from 1.4.1 to 1.4.2 in /dashboardv2/public/js/external_lib/atlas-lineage
dependabot[bot] opened a new pull request, #208: URL: https://github.com/apache/atlas/pull/208 Bumps [loader-utils](https://github.com/webpack/loader-utils) from 1.4.1 to 1.4.2. Release notes Sourced from https://github.com/webpack/loader-utils/releases;>loader-utils's releases. v1.4.2 https://github.com/webpack/loader-utils/compare/v1.4.1...v1.4.2;>1.4.2 (2022-11-11) Bug Fixes ReDoS problem (https://github-redirect.dependabot.com/webpack/loader-utils/issues/226;>#226) (https://github.com/webpack/loader-utils/commit/17cbf8fa8989c1cb45bdd2997aa524729475f1fa;>17cbf8f) Changelog Sourced from https://github.com/webpack/loader-utils/blob/v1.4.2/CHANGELOG.md;>loader-utils's changelog. https://github.com/webpack/loader-utils/compare/v1.4.1...v1.4.2;>1.4.2 (2022-11-11) Bug Fixes ReDoS problem (https://github-redirect.dependabot.com/webpack/loader-utils/issues/226;>#226) (https://github.com/webpack/loader-utils/commit/17cbf8fa8989c1cb45bdd2997aa524729475f1fa;>17cbf8f) Commits https://github.com/webpack/loader-utils/commit/331ad5067d9a1a7b8d646692e6959639969210d1;>331ad50 chore(release): 1.4.2 https://github.com/webpack/loader-utils/commit/17cbf8fa8989c1cb45bdd2997aa524729475f1fa;>17cbf8f fix: ReDoS problem (https://github-redirect.dependabot.com/webpack/loader-utils/issues/226;>#226) See full diff in https://github.com/webpack/loader-utils/compare/v1.4.1...v1.4.2;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/atlas/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@atlas.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (ATLAS-4445) unable to run import-hive.sh successfully
[
https://issues.apache.org/jira/browse/ATLAS-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635197#comment-17635197
]
ASF subversion and git services commented on ATLAS-4445:
Commit 567ffb4089f9f024049ad88a56faf3783ddd9258 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=567ffb408 ]
ATLAS-4445: fix import-hive.sh failure; updated hive version from 3.1.0 to 3.1.2
(cherry picked from commit 1a5bf676218d371398e700c1a348a60c11c52867)
> unable to run import-hive.sh successfully
> -
>
> Key: ATLAS-4445
> URL: https://issues.apache.org/jira/browse/ATLAS-4445
> Project: Atlas
> Issue Type: Bug
> Components: hive-integration
>Affects Versions: 2.2.0
> Environment: RHEL 7.x
>Reporter: Tim Hunter
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 2.3.0
>
> Attachments: ATLAS-4445.patch
>
>
> Same configuration this worked in 2.1.0, unable to figure out why it doesn't
> in 2.2.0
>
> {{$ ./import-hive.sh $ ./import-hive.sh Using Hive configuration directory
> [/usr/local/hive/conf]Log file for import is
> /var/log/atlas/import-hive.logSLF4J: Class path contains multiple SLF4J
> bindings.SLF4J: Found binding in
> [jar:file:/usr/local/hive/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]SLF4J:
> Found binding in
> [jar:file:/home/ec2-user/hadoop-3.3.1/share/hadoop/common/lib/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]2021-10-05T12:57:32,810 INFO
> [main] org.apache.atlas.hive.bridge.HiveMetaStoreBridge - delete non existing
> flag : false 2021-10-05T12:57:32,841 INFO [main]
> org.apache.atlas.ApplicationProperties - Looking for
> atlas-application.properties in classpath2021-10-05T12:57:32,843 INFO [main]
> org.apache.atlas.ApplicationProperties - Loading atlas-application.properties
> from
> file:/opt/atlas/apache-atlas-2.2.0/conf/atlas-application.properties2021-10-05T12:57:32,903
> INFO [main] org.apache.atlas.ApplicationProperties - Using graphdb backend
> 'janus'2021-10-05T12:57:32,903 INFO [main]
> org.apache.atlas.ApplicationProperties - Using storage backend
> 'hbase2'2021-10-05T12:57:32,903 INFO [main]
> org.apache.atlas.ApplicationProperties - Using index backend
> 'solr'2021-10-05T12:57:32,903 INFO [main]
> org.apache.atlas.ApplicationProperties - Atlas is running in MODE:
> PROD.2021-10-05T12:57:32,904 INFO [main]
> org.apache.atlas.ApplicationProperties - Setting solr.wait-searcher property
> 'false'2021-10-05T12:57:32,904 INFO [main]
> org.apache.atlas.ApplicationProperties - Setting index.search.map-name
> property 'false'2021-10-05T12:57:32,904 INFO [main]
> org.apache.atlas.ApplicationProperties - Setting
> atlas.graph.index.search.max-result-set-size = 1502021-10-05T12:57:32,904
> INFO [main] org.apache.atlas.ApplicationProperties - Setting
> atlas.graph.index.search.solr.wait-searcher = false2021-10-05T12:57:32,905
> INFO [main] org.apache.atlas.ApplicationProperties - Property (set to
> default) atlas.graph.cache.db-cache = true2021-10-05T12:57:32,905 INFO [main]
> org.apache.atlas.ApplicationProperties - Property (set to default)
> atlas.graph.cache.db-cache-clean-wait = 202021-10-05T12:57:32,905 INFO [main]
> org.apache.atlas.ApplicationProperties - Property (set to default)
> atlas.graph.cache.db-cache-size = 0.52021-10-05T12:57:32,905 INFO [main]
> org.apache.atlas.ApplicationProperties - Property (set to default)
> atlas.graph.cache.tx-cache-size = 150002021-10-05T12:57:32,905 INFO [main]
> org.apache.atlas.ApplicationProperties - Property (set to default)
> atlas.graph.cache.tx-dirty-size = 120Enter username for atlas :- adminEnter
> password for atlas :- Exception in thread "main"
> java.lang.NoClassDefFoundError: javax/ws/rs/core/Link$Builder at
> java.lang.Class.getDeclaredConstructors0(Native Method) at
> java.lang.Class.privateGetDeclaredConstructors(Class.java:2671) at
> java.lang.Class.getConstructor0(Class.java:3075) at
> java.lang.Class.newInstance(Class.java:412) at
> javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:65) at
> javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:117) at
> javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:105) at
> javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:91) at
> javax.ws.rs.core.MediaType.(MediaType.java:44) at
> com.sun.jersey.core.header.MediaTypes.(MediaTypes.java:65) at
> com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFactory.java:182)
> at
>
[jira] [Commented] (ATLAS-4241) import-hbase.sh get map error
[ https://issues.apache.org/jira/browse/ATLAS-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635199#comment-17635199 ] ASF subversion and git services commented on ATLAS-4241: Commit 7f9e980f6aee26523450fc40f7bfeb01a42842ab in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7f9e980f6 ] ATLAS-4241: fix import-hbase errors (cherry picked from commit da27bb1b497db7f234c66203255a3ded37af3631) > import-hbase.sh get map error > - > > Key: ATLAS-4241 > URL: https://issues.apache.org/jira/browse/ATLAS-4241 > Project: Atlas > Issue Type: Bug > Components: hbase-integration >Affects Versions: 2.1.0 >Reporter: junsionzhang >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.3.0 > > Attachments: ATLAS-4241.patch > > > when run import-hbase.sh ,errors is as follows: > 2021-04-12 14:34:25,865 ERROR - [main:] ~ ImportHBaseEntities failed > (HBaseBridge:197) > org.apache.atlas.AtlasException: Failed to load application properties > at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:147) > at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:100) > at org.apache.atlas.hbase.bridge.HBaseBridge.main(HBaseBridge.java:139) > Caused by: org.apache.commons.configuration.ConversionException: > 'atlas.graph.index.search.solr.wait-searcher' doesn't map to a List object: > true, a java.lang.Boolean > at > org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1144) > at > org.apache.commons.configuration.AbstractConfiguration.getList(AbstractConfiguration.java:1109) > at > org.apache.commons.configuration.AbstractConfiguration.interpolatedConfiguration(AbstractConfiguration.java:1274) > at org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:142) > ... 2 more > > It seems the common-configuration does not work correctly . the hbasebridge > use common-configuration 1.10 ,but the version also exists. could somebody > upgrade from 1.x to 2.x > > https://commons.apache.org/proper/commons-configuration/userguide/upgradeto2_0.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-3820) run import-kafka.sh throws Expection
[ https://issues.apache.org/jira/browse/ATLAS-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635200#comment-17635200 ] ASF subversion and git services commented on ATLAS-3820: Commit fcbc016451ae1a1dc996fbafe677a8a8806d764f in atlas's branch refs/heads/master from Madhan Neethiraj [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=fcbc01645 ] ATLAS-3820: fix import-kafka.sh failures; updated docker setup for Kafka bridge (cherry picked from commit 2c2d9197e68b809198d6e9f1232473d1c2d9e960) > run import-kafka.sh throws Expection > > > Key: ATLAS-3820 > URL: https://issues.apache.org/jira/browse/ATLAS-3820 > Project: Atlas > Issue Type: Bug > Components: kafka-integration >Affects Versions: 1.0.0 > Environment: Kafka version: 1.1.0 >Reporter: fa >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 2.3.0 > > Attachments: ATLAS-3820.patch > > > maven build command: mvn clean -DskipTests package -Pdist,embedded-hbase-solr > I run `bin/atlas_stat.py`, and I can see the web-ui. > Then I run > apache-atlas-1.0.0-kafka-hook/apache-atlas-kafka-hook-1.0.0/hook-bin/import-kafka.sh. > stack trace > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/commons/lang/exception/NestableRuntimeExceptionException in thread > "main" java.lang.NoClassDefFoundError: > org/apache/commons/lang/exception/NestableRuntimeException at > java.lang.ClassLoader.defineClass1(Native Method) at > java.lang.ClassLoader.defineClass(ClassLoader.java:763) at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at > java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at > java.net.URLClassLoader.access$100(URLClassLoader.java:74) at > java.net.URLClassLoader$1.run(URLClassLoader.java:369) at > java.net.URLClassLoader$1.run(URLClassLoader.java:363) at > java.security.AccessController.doPrivileged(Native Method) at > java.net.URLClassLoader.findClass(URLClassLoader.java:362) at > java.lang.ClassLoader.loadClass(ClassLoader.java:424) at > sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at > java.lang.ClassLoader.loadClass(ClassLoader.java:357) at > java.lang.ClassLoader.defineClass1(Native Method) at > java.lang.ClassLoader.defineClass(ClassLoader.java:763) at > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at > java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at > java.net.URLClassLoader.access$100(URLClassLoader.java:74) at > java.net.URLClassLoader$1.run(URLClassLoader.java:369) at > java.net.URLClassLoader$1.run(URLClassLoader.java:363) at > java.security.AccessController.doPrivileged(Native Method) at > java.net.URLClassLoader.findClass(URLClassLoader.java:362) at > java.lang.ClassLoader.loadClass(ClassLoader.java:424) at > sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at > java.lang.ClassLoader.loadClass(ClassLoader.java:357) at > org.apache.atlas.kafka.bridge.KafkaBridge.main(KafkaBridge.java:100)Caused > by: java.lang.ClassNotFoundException: > org.apache.commons.lang.exception.NestableRuntimeException at > java.net.URLClassLoader.findClass(URLClassLoader.java:382) at > java.lang.ClassLoader.loadClass(ClassLoader.java:424) at > sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at > java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 25 more -- This message was sent by Atlassian Jira (v8.20.10#820010)
