[jira] [Commented] (ATLAS-4740) support build using higher version JDK, with 1.8 as target version
[
https://issues.apache.org/jira/browse/ATLAS-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17708692#comment-17708692
]
ASF subversion and git services commented on ATLAS-4740:
Commit 7ab30522583167bb663b3ee7032a7b71a28025b5 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=7ab305225 ]
ATLAS-4740: enable building Atlas using JDK versions higher than 8
> support build using higher version JDK, with 1.8 as target version
> --
>
> Key: ATLAS-4740
> URL: https://issues.apache.org/jira/browse/ATLAS-4740
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
>
> Atlas requires JDK8 to build. Recent changes in infra, like Jenkins, require
> using JDK11 or above to build. Building with JDK8 results in the failure
> given below.
>
> To address this issue, Atlas should be updated to build using later version
> JDK, still continuing to generate libraries for JDK8.
>
> {noformat}
> [Atlas-master-snapshot-publish] $ /home/jenkins/tools/java/latest1.8/bin/java
> -Xmx16g -Xms16g -Dfile.encoding=UTF-8 -Dproject.build.sourceEncoding=UTF-8
> -cp
> /home/jenkins/maven35-agent.jar:/home/jenkins/tools/maven/apache-maven-3.6.3/boot/plexus-classworlds-2.6.0.jar:/home/jenkins/tools/maven/apache-maven-3.6.3/conf/logging
> jenkins.maven3.agent.Maven35Main
> /home/jenkins/tools/maven/apache-maven-3.6.3 /home/jenkins/agent.jar
> /home/jenkins/maven35-interceptor.jar
> /home/jenkins/maven3-interceptor-commons.jar 36489
> Exception in thread "main" java.lang.UnsupportedClassVersionError:
> hudson/remoting/Launcher has been compiled by a more recent version of the
> Java Runtime (class file version 55.0), this version of the Java Runtime only
> recognizes class file versions up to 52.0
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4732) UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date entries
[
https://issues.apache.org/jira/browse/ATLAS-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17708668#comment-17708668
]
Prasad P. Pawar commented on ATLAS-4732:
Hi,
Uploaded patch has the required date issue fixed.
> UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date
> entries
> --
>
> Key: ATLAS-4732
> URL: https://issues.apache.org/jira/browse/ATLAS-4732
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4732-UI-Setting-atlas.ui.date.format-to-certai.patch
>
>
> Pre-conditions:
> In atlas-application.properties, set the following:-
> {code:java}
> atlas.ui.date.format=DD/MM/ hh:mm:ss{code}
> Steps:
> 1. Create Business Metadata with a date type and assign to a Type (e.g.
> hdfs_path)
> 2. Create an entity for the assigned Type (hdfs_path).
> 3. Add Business Metadata and select the created date type.
> 4. Populate this value with a date in DD/MM/ format, i.e. (06/03/2023)
> 5. Click Apply.
> 6. Click Save.
> The date changes to 03/06/2023 which is a completely different date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4732) UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date entries
[
https://issues.apache.org/jira/browse/ATLAS-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4732:
---
Attachment: 0001-ATLAS-4732-UI-Setting-atlas.ui.date.format-to-certai.patch
> UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date
> entries
> --
>
> Key: ATLAS-4732
> URL: https://issues.apache.org/jira/browse/ATLAS-4732
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Major
> Attachments:
> 0001-ATLAS-4732-UI-Setting-atlas.ui.date.format-to-certai.patch
>
>
> Pre-conditions:
> In atlas-application.properties, set the following:-
> {code:java}
> atlas.ui.date.format=DD/MM/ hh:mm:ss{code}
> Steps:
> 1. Create Business Metadata with a date type and assign to a Type (e.g.
> hdfs_path)
> 2. Create an entity for the assigned Type (hdfs_path).
> 3. Add Business Metadata and select the created date type.
> 4. Populate this value with a date in DD/MM/ format, i.e. (06/03/2023)
> 5. Click Apply.
> 6. Click Save.
> The date changes to 03/06/2023 which is a completely different date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (ATLAS-4732) UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date entries
[
https://issues.apache.org/jira/browse/ATLAS-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar reassigned ATLAS-4732:
--
Assignee: Prasad P. Pawar
> UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date
> entries
> --
>
> Key: ATLAS-4732
> URL: https://issues.apache.org/jira/browse/ATLAS-4732
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Prasad P. Pawar
>Priority: Major
>
> Pre-conditions:
> In atlas-application.properties, set the following:-
> {code:java}
> atlas.ui.date.format=DD/MM/ hh:mm:ss{code}
> Steps:
> 1. Create Business Metadata with a date type and assign to a Type (e.g.
> hdfs_path)
> 2. Create an entity for the assigned Type (hdfs_path).
> 3. Add Business Metadata and select the created date type.
> 4. Populate this value with a date in DD/MM/ format, i.e. (06/03/2023)
> 5. Click Apply.
> 6. Click Save.
> The date changes to 03/06/2023 which is a completely different date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4741) Build failure: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
[
https://issues.apache.org/jira/browse/ATLAS-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707776#comment-17707776
]
ASF subversion and git services commented on ATLAS-4741:
Commit 211aa719e703c83327610d0c2efad1b9372f80e1 in atlas's branch
refs/heads/branch-2.0 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=211aa719e ]
ATLAS-4741: updated Storm version to 2.4.0
(cherry picked from commit 92861ba9f3a12c7df364a8ae4c5ef378e9171424)
> Build failure: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
> --
>
> Key: ATLAS-4741
> URL: https://issues.apache.org/jira/browse/ATLAS-4741
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4741.patch
>
>
> Atlas build fails with the following error:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> (process-resource-bundles) on project storm-bridge-shim: Error resolving
> project artifact: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
> from/to java.net-Public (https://maven.java.net/content/groups/public/):
> transfer failed for
> https://maven.java.net/content/groups/public/com/twitter/carbonite/1.5.0/carbonite-1.5.0.pom
> for project com.twitter:carbonite:jar:1.5.0: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target -> [Help 1]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4741) Build failure: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
[
https://issues.apache.org/jira/browse/ATLAS-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707775#comment-17707775
]
ASF subversion and git services commented on ATLAS-4741:
Commit 92861ba9f3a12c7df364a8ae4c5ef378e9171424 in atlas's branch
refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=92861ba9f ]
ATLAS-4741: updated Storm version to 2.4.0
> Build failure: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
> --
>
> Key: ATLAS-4741
> URL: https://issues.apache.org/jira/browse/ATLAS-4741
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Affects Versions: 3.0.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: ATLAS-4741.patch
>
>
> Atlas build fails with the following error:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> (process-resource-bundles) on project storm-bridge-shim: Error resolving
> project artifact: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
> from/to java.net-Public (https://maven.java.net/content/groups/public/):
> transfer failed for
> https://maven.java.net/content/groups/public/com/twitter/carbonite/1.5.0/carbonite-1.5.0.pom
> for project com.twitter:carbonite:jar:1.5.0: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target -> [Help 1]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: (was: 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch) > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4741) Build failure: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
Madhan Neethiraj created ATLAS-4741:
---
Summary: Build failure: Could not transfer artifact
com.twitter:carbonite:pom:1.5.0
Key: ATLAS-4741
URL: https://issues.apache.org/jira/browse/ATLAS-4741
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
Atlas build fails with the following error:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(process-resource-bundles) on project storm-bridge-shim: Error resolving
project artifact: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
from/to java.net-Public (https://maven.java.net/content/groups/public/):
transfer failed for
https://maven.java.net/content/groups/public/com/twitter/carbonite/1.5.0/carbonite-1.5.0.pom
for project com.twitter:carbonite:jar:1.5.0: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target -> [Help 1]
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4740) support build using higher version JDK, with 1.8 as target version
Madhan Neethiraj created ATLAS-4740:
---
Summary: support build using higher version JDK, with 1.8 as
target version
Key: ATLAS-4740
URL: https://issues.apache.org/jira/browse/ATLAS-4740
Project: Atlas
Issue Type: Improvement
Components: atlas-core
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
Atlas requires JDK8 to build. Recent changes in infra, like Jenkins, require
using JDK11 or above to build. Building with JDK8 results in the failure given
below.
To address this issue, Atlas should be updated to build using later version
JDK, still continuing to generate libraries for JDK8.
{noformat}
[Atlas-master-snapshot-publish] $ /home/jenkins/tools/java/latest1.8/bin/java
-Xmx16g -Xms16g -Dfile.encoding=UTF-8 -Dproject.build.sourceEncoding=UTF-8 -cp
/home/jenkins/maven35-agent.jar:/home/jenkins/tools/maven/apache-maven-3.6.3/boot/plexus-classworlds-2.6.0.jar:/home/jenkins/tools/maven/apache-maven-3.6.3/conf/logging
jenkins.maven3.agent.Maven35Main /home/jenkins/tools/maven/apache-maven-3.6.3
/home/jenkins/agent.jar /home/jenkins/maven35-interceptor.jar
/home/jenkins/maven3-interceptor-commons.jar 36489
Exception in thread "main" java.lang.UnsupportedClassVersionError:
hudson/remoting/Launcher has been compiled by a more recent version of the Java
Runtime (class file version 55.0), this version of the Java Runtime only
recognizes class file versions up to 52.0
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch, > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: (was: 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch) > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch, > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: (was: 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch) > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch, > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch, > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4739) Log4j migration: Replace DailyRollingFileAppender with RollingFileAppender
Disha Talreja created ATLAS-4739:
Summary: Log4j migration: Replace DailyRollingFileAppender with
RollingFileAppender
Key: ATLAS-4739
URL: https://issues.apache.org/jira/browse/ATLAS-4739
Project: Atlas
Issue Type: Sub-task
Components: atlas-core
Reporter: Disha Talreja
Assignee: Disha Talreja
Log4j 1.x provides a class
[{{org.apache.log4j.DailyRollingFileAppender}}|https://logging.apache.org/log4j/1.2/apidocs/]
which is no longer supported by Log4j 2.x. Hence, DailyRollingFileAppender
needs to be replaced by a custom rolling file appender supported by log4j2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (ATLAS-4734) HiveProcess - Output entity creation is ignored in case of same entity exists both inputs and outputs from context
[
https://issues.apache.org/jira/browse/ATLAS-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radhika Kundam closed ATLAS-4734.
-
> HiveProcess - Output entity creation is ignored in case of same entity exists
> both inputs and outputs from context
> --
>
> Key: ATLAS-4734
> URL: https://issues.apache.org/jira/browse/ATLAS-4734
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
>
> Lineage is not generated while using INSERT OVERWRITE with UNION and LEFT
> JOIN.
> {code:java}
> INSERT OVERWRITE TABLE tblB SELECT id, name, email FROM tblA UNION SELECT
> B.id, B.name, B.email FROM tblB B LEFT JOIN tblA A ON B.id=A.id; {code}
> In this scenario Hive context will be sending inputs as tblA & tblB and
> outputs as tblB.
> While processing these inputs and outputs since tblB is already processed as
> part of inputs, it's getting ignored while processing as part of outputs.
> Because of that hive_process entity is missing outputs entity details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4738) Dynamic Index Recovery issues and improvements
[
https://issues.apache.org/jira/browse/ATLAS-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radhika Kundam updated ATLAS-4738:
--
Description:
# Though there is no issues with SOLR, on Atlas startup Index recovery is
getting started as it's considering 1970-01-01T00:00:00Z as default recovery
start time.
When no index recovery data is available by default it'll consider recovery
start time based on TTL i.e., (current time - tx.log TTL).
By default SOLR tx.log default ttl is configured as 10days.
2. Custom start time configuration atlas.graph.index.recovery.start.time is not
working as it conflicts with janusgraph internal configurations. This config
should be updated to *atlas.index.recovery.start.time*
3. When SOLR went down with existing architecture we note down start time with
a buffer of solr health checkup frequency which will be (current time -
retrytime of solr health). To avoid any possible corner case scenarios updating
the buffer two times of retry time so next recovery start time should be
(current time - 2 * retry time)
4. Added REST support for index recovery which can give more flexibility to the
customer to start index recovery on-demand and will be valubale feature.
a. Get index recovery timing details
API: GET api/atlas/v2/indexrecovery/
Response:
{ "Latest start time": "2023-03-25T20:34:59.704Z", => Start
time of recent/upcoming Index recovery
"On-demand start time":
"2023-03-24T06:17:23.656Z", => Start time of index recovery requested through
REST API
"Previous start time": "2023-03-25T20:24:51.583Z"
=> Start time of previous index recovery
}
b. Start index recovery at a specific time
API: POST
api/atlas/v2/indexrecovery/start?startTime=2023-03-24T06:17:23.656Z
Response:
On success => 200 OK
On empty start Time => 400 Bad request
On Index recovery failure => 500 Internal Server Error
was:
# Though there is no issues with SOLR, on Atlas startup Index recovery is
getting started as it's considering 1970-01-01T00:00:00Z as default recovery
start time. When no index recovery data is available by default it'll consider
recovery start time based on TTL i.e., (current time - tx.log TTL).
By default SOLR tx.log default ttl is configured as 10days.
2. Custom start time configuration atlas.graph.index.recovery.start.time is not
working as it conflicts with janusgraph internal configurations. This config
should be updated to *atlas.index.recovery.start.time*
3. When SOLR went down with existing architecture we note down start time with
a buffer of solr health checkup frequency which will be (current time -
retrytime of solr health). To avoid any possible corner case scenarios updating
the buffer two times of retry time so next recovery start time should be
(current time - 2 * retry time)
4. Added REST support for index recovery which can give more flexibility to the
user to start index recovery on-demand and will be valuable feature.
a. Get index recovery timing details
API: GET api/atlas/v2/indexrecovery/
Response:
\{ "Latest start time": "2023-03-25T20:34:59.704Z",
"On-demand start time": "2023-03-24T06:17:23.656Z", "Previous start
time": "2023-03-25T20:24:51.583Z" }
b. Start index recovery at a specific time
API: POST
api/atlas/v2/indexrecovery/start?startTime=2023-03-24T06:17:23.656Z
Response:
On success => 200 OK
On empty start Time => 400 Bad request
On Index recovery failure => 500 Internal Server Error
> Dynamic Index Recovery issues and improvements
> --
>
> Key: ATLAS-4738
> URL: https://issues.apache.org/jira/browse/ATLAS-4738
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> # Though there is no issues with SOLR, on Atlas startup Index recovery is
> getting started as it's considering 1970-01-01T00:00:00Z as default recovery
> start time.
> When no index recovery data is available by default it'll consider
> recovery start time based on TTL i.e., (current time - tx.log TTL).
> By default SOLR tx.log default ttl is configured as 10days.
> 2. Custom start time configuration atlas.graph.index.recovery.start.time is
> not working as it conflicts with janusgraph internal configurat
[jira] [Updated] (ATLAS-4738) Dynamic Index Recovery issues and improvements
[
https://issues.apache.org/jira/browse/ATLAS-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radhika Kundam updated ATLAS-4738:
--
Description:
# Though there is no issues with SOLR, on Atlas startup Index recovery is
getting started as it's considering 1970-01-01T00:00:00Z as default recovery
start time. When no index recovery data is available by default it'll consider
recovery start time based on TTL i.e., (current time - tx.log TTL).
By default SOLR tx.log default ttl is configured as 10days.
2. Custom start time configuration atlas.graph.index.recovery.start.time is not
working as it conflicts with janusgraph internal configurations. This config
should be updated to *atlas.index.recovery.start.time*
3. When SOLR went down with existing architecture we note down start time with
a buffer of solr health checkup frequency which will be (current time -
retrytime of solr health). To avoid any possible corner case scenarios updating
the buffer two times of retry time so next recovery start time should be
(current time - 2 * retry time)
4. Added REST support for index recovery which can give more flexibility to the
user to start index recovery on-demand and will be valuable feature.
a. Get index recovery timing details
API: GET api/atlas/v2/indexrecovery/
Response:
\{ "Latest start time": "2023-03-25T20:34:59.704Z",
"On-demand start time": "2023-03-24T06:17:23.656Z", "Previous start
time": "2023-03-25T20:24:51.583Z" }
b. Start index recovery at a specific time
API: POST
api/atlas/v2/indexrecovery/start?startTime=2023-03-24T06:17:23.656Z
Response:
On success => 200 OK
On empty start Time => 400 Bad request
On Index recovery failure => 500 Internal Server Error
was:
1. Though there is no issues with SOLR, on Atlas startup Index recovery is
getting started as it's considering 1970-01-01T00:00:00Z as default recovery
start time. When no index recovery data is available by default it'll consider
recovery start time based on TTL i.e., (current time - tx.log TTL).
By default SOLR tx.log default ttl is configured as 10days.
2. Custom start time configuration atlas.graph.index.recovery.start.time is not
working as it conflicts with janusgraph internal configurations. This config
should be updated to *atlas.index.recovery.start.time*
3. When SOLR went down with existing architecture we note down start time with
a buffer of solr health checkup frequency which will be (current time -
retrytime of solr health). To avoid any possible corner case scenarios updating
the buffer two times of retry time so next recovery start time should be
(current time - 2 * retry time)
4. Added REST support for index recovery which can give more flexibility to the
user to start index recovery on-demand and will be valuable feature.
a. Get index recovery timing details
API: GET api/atlas/v2/indexrecovery/
Response:
{
"Latest start time": "2023-03-25T20:34:59.704Z",
"On-demand start time": "2023-03-24T06:17:23.656Z",
"Previous start time": "2023-03-25T20:24:51.583Z"
}
b. Start index recovery at a specific time
API: POST
api/atlas/v2/indexrecovery/start?startTime=2023-03-24T06:17:23.656Z
Response:
On success => 200 OK
On empty start Time => 400 Bad request
On Index recovery failure => 500 Internal Server Error
> Dynamic Index Recovery issues and improvements
> --
>
> Key: ATLAS-4738
> URL: https://issues.apache.org/jira/browse/ATLAS-4738
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> # Though there is no issues with SOLR, on Atlas startup Index recovery is
> getting started as it's considering 1970-01-01T00:00:00Z as default recovery
> start time. When no index recovery data is available by default it'll
> consider recovery start time based on TTL i.e., (current time - tx.log TTL).
> By default SOLR tx.log default ttl is configured as 10days.
> 2. Custom start time configuration atlas.graph.index.recovery.start.time is
> not working as it conflicts with janusgraph internal configurations. This
> config should be updated to *atlas.index.recovery.start.time*
> 3. When SOLR went down with existing architecture we note down start time
> with a buffer of solr health checkup frequency which will be (current time -
> retrytime of solr health). To avoid any possible corner case scenarios
> updating the buffer
[jira] [Created] (ATLAS-4738) Dynamic Index Recovery issues and improvements
Radhika Kundam created ATLAS-4738:
-
Summary: Dynamic Index Recovery issues and improvements
Key: ATLAS-4738
URL: https://issues.apache.org/jira/browse/ATLAS-4738
Project: Atlas
Issue Type: Improvement
Components: atlas-core
Reporter: Radhika Kundam
Assignee: Radhika Kundam
1. Though there is no issues with SOLR, on Atlas startup Index recovery is
getting started as it's considering 1970-01-01T00:00:00Z as default recovery
start time. When no index recovery data is available by default it'll consider
recovery start time based on TTL i.e., (current time - tx.log TTL).
By default SOLR tx.log default ttl is configured as 10days.
2. Custom start time configuration atlas.graph.index.recovery.start.time is not
working as it conflicts with janusgraph internal configurations. This config
should be updated to *atlas.index.recovery.start.time*
3. When SOLR went down with existing architecture we note down start time with
a buffer of solr health checkup frequency which will be (current time -
retrytime of solr health). To avoid any possible corner case scenarios updating
the buffer two times of retry time so next recovery start time should be
(current time - 2 * retry time)
4. Added REST support for index recovery which can give more flexibility to the
user to start index recovery on-demand and will be valuable feature.
a. Get index recovery timing details
API: GET api/atlas/v2/indexrecovery/
Response:
{
"Latest start time": "2023-03-25T20:34:59.704Z",
"On-demand start time": "2023-03-24T06:17:23.656Z",
"Previous start time": "2023-03-25T20:24:51.583Z"
}
b. Start index recovery at a specific time
API: POST
api/atlas/v2/indexrecovery/start?startTime=2023-03-24T06:17:23.656Z
Response:
On success => 200 OK
On empty start Time => 400 Bad request
On Index recovery failure => 500 Internal Server Error
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4734) HiveProcess - Output entity creation is ignored in case of same entity exists both inputs and outputs from context
[
https://issues.apache.org/jira/browse/ATLAS-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705688#comment-17705688
]
ASF subversion and git services commented on ATLAS-4734:
Commit 2d62af9326eab0312e0a6fac8ef388b1f4d0f498 in atlas's branch
refs/heads/branch-2.0 from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2d62af932 ]
ATLAS-4734: HiveProcess - Output entity creation is ignored in case of same
entity exists both inputs and outputs from context
(cherry picked from commit 013c8623e919b9442b440df9a605be343632dc2b)
> HiveProcess - Output entity creation is ignored in case of same entity exists
> both inputs and outputs from context
> --
>
> Key: ATLAS-4734
> URL: https://issues.apache.org/jira/browse/ATLAS-4734
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Lineage is not generated while using INSERT OVERWRITE with UNION and LEFT
> JOIN.
> {code:java}
> INSERT OVERWRITE TABLE tblB SELECT id, name, email FROM tblA UNION SELECT
> B.id, B.name, B.email FROM tblB B LEFT JOIN tblA A ON B.id=A.id; {code}
> In this scenario Hive context will be sending inputs as tblA & tblB and
> outputs as tblB.
> While processing these inputs and outputs since tblB is already processed as
> part of inputs, it's getting ignored while processing as part of outputs.
> Because of that hive_process entity is missing outputs entity details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4734) HiveProcess - Output entity creation is ignored in case of same entity exists both inputs and outputs from context
[
https://issues.apache.org/jira/browse/ATLAS-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705685#comment-17705685
]
ASF subversion and git services commented on ATLAS-4734:
Commit 013c8623e919b9442b440df9a605be343632dc2b in atlas's branch
refs/heads/master from Radhika Kundam
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=013c8623e ]
ATLAS-4734: HiveProcess - Output entity creation is ignored in case of same
entity exists both inputs and outputs from context
> HiveProcess - Output entity creation is ignored in case of same entity exists
> both inputs and outputs from context
> --
>
> Key: ATLAS-4734
> URL: https://issues.apache.org/jira/browse/ATLAS-4734
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Radhika Kundam
>Assignee: Radhika Kundam
>Priority: Major
>
> Lineage is not generated while using INSERT OVERWRITE with UNION and LEFT
> JOIN.
> {code:java}
> INSERT OVERWRITE TABLE tblB SELECT id, name, email FROM tblA UNION SELECT
> B.id, B.name, B.email FROM tblB B LEFT JOIN tblA A ON B.id=A.id; {code}
> In this scenario Hive context will be sending inputs as tblA & tblB and
> outputs as tblB.
> While processing these inputs and outputs since tblB is already processed as
> part of inputs, it's getting ignored while processing as part of outputs.
> Because of that hive_process entity is missing outputs entity details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4737) Image for Iceberg table and Iceberg column
Farhan Khan created ATLAS-4737: -- Summary: Image for Iceberg table and Iceberg column Key: ATLAS-4737 URL: https://issues.apache.org/jira/browse/ATLAS-4737 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Farhan Khan Image for new types(Iceberg table and Iceberg column) needs to added as currently it is showing as blank in Atlas UI -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4737) Image for Iceberg table and Iceberg column
[ https://issues.apache.org/jira/browse/ATLAS-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan reassigned ATLAS-4737: -- Assignee: Farhan Khan > Image for Iceberg table and Iceberg column > -- > > Key: ATLAS-4737 > URL: https://issues.apache.org/jira/browse/ATLAS-4737 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Minor > > Image for new types(Iceberg table and Iceberg column) needs to added as > currently it is showing as blank in Atlas UI -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704489#comment-17704489
]
ASF subversion and git services commented on ATLAS-4736:
Commit e1294c04a4db2cf24d79a50f89365cf3a9213013 in atlas's branch
refs/heads/branch-2.0 from Prasad Pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=e1294c04a ]
ATLAS-4736:Audit tab reporting a date of 1970 in a few properties.
Signed-off-by: Prasad Pawar
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704488#comment-17704488
]
ASF subversion and git services commented on ATLAS-4736:
Commit c78f3cb1af4f5b15bbd092d45d0cb7b6cc763843 in atlas's branch
refs/heads/master from Prasad Pawar
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=c78f3cb1a ]
ATLAS-4736:Audit tab reporting a date of 1970 in a few properties.
Signed-off-by: Prasad Pawar
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704459#comment-17704459
]
Rahul Kurup commented on ATLAS-4736:
+1
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703913#comment-17703913
]
Rahul Kurup commented on ATLAS-4736:
Hi, if I add a date value that is before 1970 (negative epoch milliseconds) eg:
-2452140, then the date appears as N/A.
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Attachment: (was:
0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch)
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Attachment: 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703342#comment-17703342
]
Prasad P. Pawar edited comment on ATLAS-4736 at 3/23/23 4:52 AM:
-
Hi,
Uploaded patch had the required fix, the date will be display as per the
response value,
if the datatype is date, it will display as per the date format of
"atlas.ui.date.format" from session API.
was (Author: prasadpp13):
Hi,
Uploaded path had the required fix, the date will be display as per the
response value,
if the datatype is date, it will display as per the date format of
"atlas.ui.date.format" from session API.
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703342#comment-17703342
]
Prasad P. Pawar commented on ATLAS-4736:
Hi,
Uploaded path had the required fix, the date will be display as per the
response value,
if the datatype is date, it will display as per the date format of
"atlas.ui.date.format" from session API.
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Attachment: 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments:
> 0001-ATLAS-4736-Audit-tab-reporting-a-date-of-1970-in-a-f.patch,
> audit_expand_showing_date_issue.png, entity_audit_tab.png,
> entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Attachment: entity_properties_tab_date.png
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments: audit_expand_showing_date_issue.png,
> entity_audit_tab.png, entity_properties_tab_date.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Attachment: audit_expand_showing_date_issue.png
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments: audit_expand_showing_date_issue.png, entity_audit_tab.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Attachment: entity_audit_tab.png
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
> Attachments: entity_audit_tab.png
>
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Attachment: (was: Screenshot from 2023-03-21 19-26-44.png)
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Attachment: Screenshot from 2023-03-21 19-26-44.png
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Labels: Atlas-UI audit (was: )
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
> Labels: Atlas-UI, audit
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[
https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-4736:
---
Description:
Create entities using the following data in POST command with the "typeName"
called "DateTimeCheck".
typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
"syncJobCreateTimeInText" is string.
{code:java}
POST :
--data-raw ' {
"entity": {
"typeName": "DateTimeCheck",
"attributes": {
"syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
"UpdateTime": null,
"syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
"syncJobCreateTime": "0",
"CreatedByUserId": "admin",
"Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
"description": "ENTITY_FOR_DATE_TIME_CHECK",
"syncJobUpdatedByUserId": null,
"CreateTimeInText": "2022-12-21 09:01:36 CDT",
"syncJobCreatedByUserId": null,
"syncJobType": "fullSync",
"syncJobUpdateTime": 1671649924455,
"name": "ENTITY_FOR_DATE_TIME_CHECK",
"additionalProperties": {
"authDatabase": null,
"catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
"database": null,
"host": null,
"ownerId": "1000331095",
"ssl": "false",
"username": null
},
"CreatedBy": "1000331095",
"CreateTime": 1628085696000
}
}
}' {code}
After the entity is posted, the Atlas audit tab is reporting
"CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
created on the year of 1970.
> Atlas UI: Audit tab reporting a date of 1970 in a few properties.
> -
>
> Key: ATLAS-4736
> URL: https://issues.apache.org/jira/browse/ATLAS-4736
> Project: Atlas
> Issue Type: Bug
> Components: atlas-webui
>Reporter: Prasad P. Pawar
>Assignee: Prasad P. Pawar
>Priority: Major
>
> Create entities using the following data in POST command with the "typeName"
> called "DateTimeCheck".
> typedef for "CreateTimeInText", "syncJobUpdateTimeInText" &
> "syncJobCreateTimeInText" is string.
> {code:java}
> POST :
> --data-raw ' {
> "entity": {
> "typeName": "DateTimeCheck",
> "attributes": {
> "syncJobUpdateTimeInText": "2022-12-21 09:01:36 CDT",
> "UpdateTime": null,
> "syncJobCreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreateTime": "0",
> "CreatedByUserId": "admin",
> "Guid": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "description": "ENTITY_FOR_DATE_TIME_CHECK",
> "syncJobUpdatedByUserId": null,
> "CreateTimeInText": "2022-12-21 09:01:36 CDT",
> "syncJobCreatedByUserId": null,
> "syncJobType": "fullSync",
> "syncJobUpdateTime": 1671649924455,
> "name": "ENTITY_FOR_DATE_TIME_CHECK",
> "additionalProperties": {
> "authDatabase": null,
> "catalogId": "cc519d95-5dd5-4646-b1b3-0eae280208e6",
> "database": null,
> "host": null,
> "ownerId": "1000331095",
> "ssl": "false",
> "username": null
> },
> "CreatedBy": "1000331095",
> "CreateTime": 1628085696000
> }
> }
> }' {code}
> After the entity is posted, the Atlas audit tab is reporting
> "CreateTimeInText", "syncJobUpdateTimeInText", and "syncJobCreateTimeInText "
> created on the year of 1970.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1970 in a few properties.
[ https://issues.apache.org/jira/browse/ATLAS-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar updated ATLAS-4736: --- Summary: Atlas UI: Audit tab reporting a date of 1970 in a few properties. (was: Atlas UI: Audit tab reporting a date of 1969 in a few properties.) > Atlas UI: Audit tab reporting a date of 1970 in a few properties. > - > > Key: ATLAS-4736 > URL: https://issues.apache.org/jira/browse/ATLAS-4736 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4736) Atlas UI: Audit tab reporting a date of 1969 in a few properties.
Prasad P. Pawar created ATLAS-4736: -- Summary: Atlas UI: Audit tab reporting a date of 1969 in a few properties. Key: ATLAS-4736 URL: https://issues.apache.org/jira/browse/ATLAS-4736 Project: Atlas Issue Type: Bug Components: atlas-webui Reporter: Prasad P. Pawar Assignee: Prasad P. Pawar -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4534) entity was deleted when edit entity by UI
[ https://issues.apache.org/jira/browse/ATLAS-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703061#comment-17703061 ] Joseph Zhang commented on ATLAS-4534: - here is workaround. when we define a COPOSITION relationship, isLegacyAttribute must be set to true for both end. or else when we edit the container entity, code will validate the children entities and found that children not existing (because legacy attributes is false and not shown at container entity attributes), then code marked container entity as DELETED and save it > entity was deleted when edit entity by UI > - > > Key: ATLAS-4534 > URL: https://issues.apache.org/jira/browse/ATLAS-4534 > Project: Atlas > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Joseph Zhang >Priority: Critical > > hi all, > I'm using the atlas version 2.2.0, when I edit entity attribute value by > using the edit button on UI, the entity was deleted instead, status change to > "DELETED". > I did not figure out how this happened, the debug info as below. Please help > me on this. thanks in advance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: (was: 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch) > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: (was: 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch) > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U-1.patch, > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: (was: 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch) > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan updated ATLAS-4735: --- Attachment: 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > Attachments: > 0001-ATLAS-4735-Ability-to-download-search-results-from-U.patch > > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4735) Ability to download search results from UI
Farhan Khan created ATLAS-4735: -- Summary: Ability to download search results from UI Key: ATLAS-4735 URL: https://issues.apache.org/jira/browse/ATLAS-4735 Project: Atlas Issue Type: New Feature Components: atlas-webui Reporter: Farhan Khan Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4735) Ability to download search results from UI
[ https://issues.apache.org/jira/browse/ATLAS-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farhan Khan reassigned ATLAS-4735: -- Assignee: Farhan Khan > Ability to download search results from UI > -- > > Key: ATLAS-4735 > URL: https://issues.apache.org/jira/browse/ATLAS-4735 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Reporter: Farhan Khan >Assignee: Farhan Khan >Priority: Major > > Feature to download search results from UI in .csv format. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4734) HiveProcess - Output entity creation is ignored in case of same entity exists both inputs and outputs from context
Radhika Kundam created ATLAS-4734:
-
Summary: HiveProcess - Output entity creation is ignored in case
of same entity exists both inputs and outputs from context
Key: ATLAS-4734
URL: https://issues.apache.org/jira/browse/ATLAS-4734
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Radhika Kundam
Assignee: Radhika Kundam
Lineage is not generated while using INSERT OVERWRITE with UNION and LEFT JOIN.
{code:java}
INSERT OVERWRITE TABLE tblB SELECT id, name, email FROM tblA UNION SELECT B.id,
B.name, B.email FROM tblB B LEFT JOIN tblA A ON B.id=A.id; {code}
In this scenario Hive context will be sending inputs as tblA & tblB and outputs
as tblB.
While processing these inputs and outputs since tblB is already processed as
part of inputs, it's getting ignored while processing as part of outputs.
Because of that hive_process entity is missing outputs entity details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4733) Download Basic and DSL search results
Mandar Ambawane created ATLAS-4733: -- Summary: Download Basic and DSL search results Key: ATLAS-4733 URL: https://issues.apache.org/jira/browse/ATLAS-4733 Project: Atlas Issue Type: Improvement Components: atlas-core Reporter: Mandar Ambawane Assignee: Mandar Ambawane This ticket tracks the Server side changes required for the Search result download task. >From server side, each download request is considered as a separate thread >which will run in the background and will generate the csv file according to >the inputs provided. The generated files will be stored in the specific location (which is configurable). A scheduler will be run to delete the old files. In this case, the scheduler interval and file expiry time is also configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4732) UI: Setting 'atlas.ui.date.format' to certain value creates incorrect date entries
Rahul Kurup created ATLAS-4732:
--
Summary: UI: Setting 'atlas.ui.date.format' to certain value
creates incorrect date entries
Key: ATLAS-4732
URL: https://issues.apache.org/jira/browse/ATLAS-4732
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
Pre-conditions:
In atlas-application.properties, set the following:-
{code:java}
atlas.ui.date.format=DD/MM/ hh:mm:ss{code}
Steps:
1. Create Business Metadata with a date type and assign to a Type (e.g.
hdfs_path)
2. Create an entity for the assigned Type (hdfs_path).
3. Add Business Metadata and select the created date type.
4. Populate this value with a date in DD/MM/ format, i.e. (06/03/2023)
5. Click Apply.
6. Click Save.
The date changes to 03/06/2023 which is a completely different date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4731) Entity fetch api call fails for some entity which has businessMetaData with Biginteger attributes
[ https://issues.apache.org/jira/browse/ATLAS-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia updated ATLAS-4731: -- Attachment: BigInt_Test_Entity_BusMeta.json BigInt_Test_Create.json > Entity fetch api call fails for some entity which has businessMetaData with > Biginteger attributes > - > > Key: ATLAS-4731 > URL: https://issues.apache.org/jira/browse/ATLAS-4731 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > Attachments: BigInt_Test_Create.json, BigInt_Test_Entity_BusMeta.json > > > Using the beta interface we can see our custom typeDefs in the left hand panel > >-- localTypeDef (1,012) > custom_typedef_a (1) > custom_typedef_b (1,008) > custom_typedef_c (3) > Selecting localTypeDev/custom__b displays the list of entities in the right > hand panel. > Selecting any of the results generates a "Something went wrong" popup, the > rotating loading icon and an unpopulated > Properties/Relationships/Classifications/Audits/Tasks page. > The following ERROR message can be seen in the ATLAS application.log :- > ERROR - [etp2052996178-280 - xnxnxxnn--nnnx-xnnn-nxnnxnnnxnnx:] ~ graph > rollback due to exception (GraphTransactionInterceptor:200) > java.lang.ArrayIndexOutOfBoundsException: Required size [1] exceeds actual > remaining size [0] > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.require(StaticArrayBuffer.java:94) > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.getByte(StaticArrayBuffer.java:170) > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.getBytes(StaticArrayBuffer.java:253) > at > org.janusgraph.diskstorage.util.ReadArrayBuffer.getBytes(ReadArrayBuffer.java:120) > at > org.janusgraph.graphdb.database.serialize.attribute.ByteArraySerializer.read(ByteArraySerializer.java:46) > at > org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:36) > at > org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:30) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectNotNullInternal(StandardSerializer.java:305) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectInternal(StandardSerializer.java:295) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObject(StandardSerializer.java:275) > at > org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:215) > at > org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:205) > at > org.janusgraph.graphdb.database.EdgeSerializer.parseRelation(EdgeSerializer.java:135) > at > org.janusgraph.graphdb.database.EdgeSerializer.readRelation(EdgeSerializer.java:135) > at > org.janusgraph.graphdb.transaction.RelationConstructor.readRelation(RelationConstructor.java:70) > at > org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:57) > at > org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:45) > at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:72) > at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:38) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusElement.getProperty(AtlasJanusElement.java:66) > at > org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.getProperty(AtlasGraphUtilsV2.java:283) > ~~ > So while writing the BusinessMetaData for BigInteger, value=4 we do not call > BigIntegerSerializer class, so i won't throw the exception. > And while access through UI it fetch data from BigintegerSerializer class and > throw the Required size [1] exceeds actual remaining size [0] exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4731) Entity fetch api call fails for some entity which has businessMetaData with Biginteger attributes
[ https://issues.apache.org/jira/browse/ATLAS-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paresh Devalia reassigned ATLAS-4731: - Assignee: Paresh Devalia > Entity fetch api call fails for some entity which has businessMetaData with > Biginteger attributes > - > > Key: ATLAS-4731 > URL: https://issues.apache.org/jira/browse/ATLAS-4731 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Paresh Devalia >Assignee: Paresh Devalia >Priority: Major > > Using the beta interface we can see our custom typeDefs in the left hand panel > >-- localTypeDef (1,012) > custom_typedef_a (1) > custom_typedef_b (1,008) > custom_typedef_c (3) > Selecting localTypeDev/custom__b displays the list of entities in the right > hand panel. > Selecting any of the results generates a "Something went wrong" popup, the > rotating loading icon and an unpopulated > Properties/Relationships/Classifications/Audits/Tasks page. > The following ERROR message can be seen in the ATLAS application.log :- > ERROR - [etp2052996178-280 - xnxnxxnn--nnnx-xnnn-nxnnxnnnxnnx:] ~ graph > rollback due to exception (GraphTransactionInterceptor:200) > java.lang.ArrayIndexOutOfBoundsException: Required size [1] exceeds actual > remaining size [0] > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.require(StaticArrayBuffer.java:94) > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.getByte(StaticArrayBuffer.java:170) > at > org.janusgraph.diskstorage.util.StaticArrayBuffer.getBytes(StaticArrayBuffer.java:253) > at > org.janusgraph.diskstorage.util.ReadArrayBuffer.getBytes(ReadArrayBuffer.java:120) > at > org.janusgraph.graphdb.database.serialize.attribute.ByteArraySerializer.read(ByteArraySerializer.java:46) > at > org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:36) > at > org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:30) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectNotNullInternal(StandardSerializer.java:305) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectInternal(StandardSerializer.java:295) > at > org.janusgraph.graphdb.database.serialize.StandardSerializer.readObject(StandardSerializer.java:275) > at > org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:215) > at > org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:205) > at > org.janusgraph.graphdb.database.EdgeSerializer.parseRelation(EdgeSerializer.java:135) > at > org.janusgraph.graphdb.database.EdgeSerializer.readRelation(EdgeSerializer.java:135) > at > org.janusgraph.graphdb.transaction.RelationConstructor.readRelation(RelationConstructor.java:70) > at > org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:57) > at > org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:45) > at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:72) > at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:38) > at > org.apache.atlas.repository.graphdb.janus.AtlasJanusElement.getProperty(AtlasJanusElement.java:66) > at > org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.getProperty(AtlasGraphUtilsV2.java:283) > ~~ > So while writing the BusinessMetaData for BigInteger, value=4 we do not call > BigIntegerSerializer class, so i won't throw the exception. > And while access through UI it fetch data from BigintegerSerializer class and > throw the Required size [1] exceeds actual remaining size [0] exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4731) Entity fetch api call fails for some entity which has businessMetaData with Biginteger attributes
Paresh Devalia created ATLAS-4731: - Summary: Entity fetch api call fails for some entity which has businessMetaData with Biginteger attributes Key: ATLAS-4731 URL: https://issues.apache.org/jira/browse/ATLAS-4731 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Paresh Devalia Using the beta interface we can see our custom typeDefs in the left hand panel >-- localTypeDef (1,012) custom_typedef_a (1) custom_typedef_b (1,008) custom_typedef_c (3) Selecting localTypeDev/custom__b displays the list of entities in the right hand panel. Selecting any of the results generates a "Something went wrong" popup, the rotating loading icon and an unpopulated Properties/Relationships/Classifications/Audits/Tasks page. The following ERROR message can be seen in the ATLAS application.log :- ERROR - [etp2052996178-280 - xnxnxxnn--nnnx-xnnn-nxnnxnnnxnnx:] ~ graph rollback due to exception (GraphTransactionInterceptor:200) java.lang.ArrayIndexOutOfBoundsException: Required size [1] exceeds actual remaining size [0] at org.janusgraph.diskstorage.util.StaticArrayBuffer.require(StaticArrayBuffer.java:94) at org.janusgraph.diskstorage.util.StaticArrayBuffer.getByte(StaticArrayBuffer.java:170) at org.janusgraph.diskstorage.util.StaticArrayBuffer.getBytes(StaticArrayBuffer.java:253) at org.janusgraph.diskstorage.util.ReadArrayBuffer.getBytes(ReadArrayBuffer.java:120) at org.janusgraph.graphdb.database.serialize.attribute.ByteArraySerializer.read(ByteArraySerializer.java:46) at org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:36) at org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:30) at org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectNotNullInternal(StandardSerializer.java:305) at org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectInternal(StandardSerializer.java:295) at org.janusgraph.graphdb.database.serialize.StandardSerializer.readObject(StandardSerializer.java:275) at org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:215) at org.janusgraph.graphdb.database.EdgeSerializer.readpropertyValue(EdgeSerializer.java:205) at org.janusgraph.graphdb.database.EdgeSerializer.parseRelation(EdgeSerializer.java:135) at org.janusgraph.graphdb.database.EdgeSerializer.readRelation(EdgeSerializer.java:135) at org.janusgraph.graphdb.transaction.RelationConstructor.readRelation(RelationConstructor.java:70) at org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:57) at org.janusgraph.graphdb.transaction.RelationConstructor$1.next(RelationConstructor.java:45) at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:72) at org.apache.tinkerpop.gremlin.structure.Vertex.property(Vertex.java:38) at org.apache.atlas.repository.graphdb.janus.AtlasJanusElement.getProperty(AtlasJanusElement.java:66) at org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.getProperty(AtlasGraphUtilsV2.java:283) ~~ So while writing the BusinessMetaData for BigInteger, value=4 we do not call BigIntegerSerializer class, so i won't throw the exception. And while access through UI it fetch data from BigintegerSerializer class and throw the Required size [1] exceeds actual remaining size [0] exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4657) Atlas Python client is messing up with logs
[
https://issues.apache.org/jira/browse/ATLAS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-4657.
-
Fix Version/s: 3.0.0
2.4.0
Resolution: Fixed
[~dolfinus] - thank you for this fix in Apache Atlas Python client. This fix
is included [Python client
0.0.13|https://pypi.org/project/apache-atlas/0.0.13/].
> Atlas Python client is messing up with logs
> ---
>
> Key: ATLAS-4657
> URL: https://issues.apache.org/jira/browse/ATLAS-4657
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 2.1.0
>Reporter: Maxim Martynov
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After importing {{atlas-client}} Python library, I got all my loggers
> disabled.
> This is caused by this code block:
> [https://github.com/apache/atlas/blob/c1daaa44c3833be31c006753a2cf2f6f2e476cdc/intg/src/main/python/apache_atlas/__init__.py]
> Unlike applications, libraries should not setup logging by themselves. It
> should be done explicitly by code which uses this client. Or there should be
> a function to set up desired logging, which also should be explicitly called
> by application or user.
>
> I've created a pull request to fix this issue:
> [https://github.com/apache/atlas/pull/157]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4657) Atlas Python client is messing up with logs
[
https://issues.apache.org/jira/browse/ATLAS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694633#comment-17694633
]
ASF subversion and git services commented on ATLAS-4657:
Commit 436753723e9419ed0c5d45db1908333def89b707 in atlas's branch
refs/heads/branch-2.0 from Maxim Martynov
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=436753723 ]
ATLAS-4657: Python client updated to not set root logging settings
Signed-off-by: Madhan Neethiraj
(cherry picked from commit 98900e3492c19d59c5cecbf8a440ae9f01578b31)
> Atlas Python client is messing up with logs
> ---
>
> Key: ATLAS-4657
> URL: https://issues.apache.org/jira/browse/ATLAS-4657
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 2.1.0
>Reporter: Maxim Martynov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After importing {{atlas-client}} Python library, I got all my loggers
> disabled.
> This is caused by this code block:
> [https://github.com/apache/atlas/blob/c1daaa44c3833be31c006753a2cf2f6f2e476cdc/intg/src/main/python/apache_atlas/__init__.py]
> Unlike applications, libraries should not setup logging by themselves. It
> should be done explicitly by code which uses this client. Or there should be
> a function to set up desired logging, which also should be explicitly called
> by application or user.
>
> I've created a pull request to fix this issue:
> [https://github.com/apache/atlas/pull/157]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4657) Atlas Python client is messing up with logs
[
https://issues.apache.org/jira/browse/ATLAS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694630#comment-17694630
]
ASF subversion and git services commented on ATLAS-4657:
Commit 98900e3492c19d59c5cecbf8a440ae9f01578b31 in atlas's branch
refs/heads/master from Maxim Martynov
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=98900e349 ]
ATLAS-4657: Python client updated to not set root logging settings
Signed-off-by: Madhan Neethiraj
> Atlas Python client is messing up with logs
> ---
>
> Key: ATLAS-4657
> URL: https://issues.apache.org/jira/browse/ATLAS-4657
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 2.1.0
>Reporter: Maxim Martynov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After importing {{atlas-client}} Python library, I got all my loggers
> disabled.
> This is caused by this code block:
> [https://github.com/apache/atlas/blob/c1daaa44c3833be31c006753a2cf2f6f2e476cdc/intg/src/main/python/apache_atlas/__init__.py]
> Unlike applications, libraries should not setup logging by themselves. It
> should be done explicitly by code which uses this client. Or there should be
> a function to set up desired logging, which also should be explicitly called
> by application or user.
>
> I've created a pull request to fix this issue:
> [https://github.com/apache/atlas/pull/157]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4657) Atlas Python client is messing up with logs
[
https://issues.apache.org/jira/browse/ATLAS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694614#comment-17694614
]
Umesh Padashetty commented on ATLAS-4657:
-
I have tested the changes, and it works fine. Logging issue is now fixed
> Atlas Python client is messing up with logs
> ---
>
> Key: ATLAS-4657
> URL: https://issues.apache.org/jira/browse/ATLAS-4657
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 2.1.0
>Reporter: Maxim Martynov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After importing {{atlas-client}} Python library, I got all my loggers
> disabled.
> This is caused by this code block:
> [https://github.com/apache/atlas/blob/c1daaa44c3833be31c006753a2cf2f6f2e476cdc/intg/src/main/python/apache_atlas/__init__.py]
> Unlike applications, libraries should not setup logging by themselves. It
> should be done explicitly by code which uses this client. Or there should be
> a function to set up desired logging, which also should be explicitly called
> by application or user.
>
> I've created a pull request to fix this issue:
> [https://github.com/apache/atlas/pull/157]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4657) Atlas Python client is messing up with logs
[
https://issues.apache.org/jira/browse/ATLAS-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694456#comment-17694456
]
Maxim Martynov commented on ATLAS-4657:
---
Can anyone review this PR?
> Atlas Python client is messing up with logs
> ---
>
> Key: ATLAS-4657
> URL: https://issues.apache.org/jira/browse/ATLAS-4657
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 2.1.0
>Reporter: Maxim Martynov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After importing {{atlas-client}} Python library, I got all my loggers
> disabled.
> This is caused by this code block:
> [https://github.com/apache/atlas/blob/c1daaa44c3833be31c006753a2cf2f6f2e476cdc/intg/src/main/python/apache_atlas/__init__.py]
> Unlike applications, libraries should not setup logging by themselves. It
> should be done explicitly by code which uses this client. Or there should be
> a function to set up desired logging, which also should be explicitly called
> by application or user.
>
> I've created a pull request to fix this issue:
> [https://github.com/apache/atlas/pull/157]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4730) Unable to assign term to custom entity with no supertype in its typdef
Rahul Kurup created ATLAS-4730:
--
Summary: Unable to assign term to custom entity with no supertype
in its typdef
Key: ATLAS-4730
URL: https://issues.apache.org/jira/browse/ATLAS-4730
Project: Atlas
Issue Type: Bug
Reporter: Rahul Kurup
When we try to assign a glossary term to an entity whose custom typedef does
not have a supertype of any existing typedef, then the following error is
encountered and the term does not get assigned.
{{invalid relationshipDef: AtlasGlossarySemanticAssignment: end type 1:
Referenceable, end type 2: AtlasGlossaryTerm}}
Sample typedef to reproduce the error is given below:
{color:#dcdcdc}{{color}
{color:#9cdcfe}"enumDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[],{color}
{color:#9cdcfe}"structDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[],{color}
{color:#9cdcfe}"classificationDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[],{color}
{color:#9cdcfe}"entityDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[{color}
{color:#d4d4d4} {color}{color:#dcdcdc}{{color}
{color:#9cdcfe}"category"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"ENTITY"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"createdBy"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"admin"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"updatedBy"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"admin"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"createTime"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}1537261952180{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"updateTime"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}1537262097732{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"version"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}3{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"name"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"CustomEntity1"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"description"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"CustomEntity1"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"typeVersion"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"1.4"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"attributeDefs"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#dcdcdc}[{color}
{color:#d4d4d4} {color}{color:#dcdcdc}{{color}
{color:#9cdcfe}"name"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"scores"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"typeName"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"int"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isOptional"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}true{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"cardinality"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"SINGLE"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"valuesMinCount"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}0{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"valuesMaxCount"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}1{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isUnique"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}false{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isIndexable"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}false{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"includeInNotification"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}false{color}
{color:#dcdcdc}},{color}
{color:#d4d4d4} {color}{color:#dcdcdc}{{color}
{color:#9cdcfe}"name"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"place"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"typeName"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"string"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"isOptional"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}true{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"cardinality"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#ce9178}"SINGLE"{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"valuesMinCount"{color}{color:#dcdcdc}:{color}{color:#d4d4d4}
{color}{color:#b5cea8}0{color}{color:#dcdcdc},{color}
{color:#9cdcfe}"valuesMaxCount"{color}{color:#dcdcdc}:{color}{color
[jira] [Commented] (ATLAS-3671) Maven Package Failure
[
https://issues.apache.org/jira/browse/ATLAS-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690364#comment-17690364
]
Nixon Rodrigues commented on ATLAS-3671:
{code:java}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 04:33 min (Wall Clock)
[INFO] Finished at: 2023-02-17T11:01:53Z
[INFO]
Error: Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(process-resource-bundles) on project storm-bridge-shim: Error resolving
project artifact: Could not transfer artifact com.twitter:carbonite:pom:1.5.0
from/to hortonworks.repo
(https://repo.hortonworks.com/content/repositories/releases): transfer failed
for
https://repo.hortonworks.com/content/repositories/releases/com/twitter/carbonite/1.5.0/carbonite-1.5.0.pom,
status: 504 Gateway Time-out for project com.twitter:carbonite:jar:1.5.0 ->
[Help 1]
Error:
Error: To see the full stack trace of the errors, re-run Maven with the -e
switch.
Error: Re-run Maven using the -X switch to enable full debug logging.
Error:
Error: For more information about the errors and possible solutions, please
read the following articles:
Error: [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Error:
Error: After correcting the problems, you can resume the build with the command
Error: mvn -rf :storm-bridge-shim{code}
> Maven Package Failure
> -
>
> Key: ATLAS-3671
> URL: https://issues.apache.org/jira/browse/ATLAS-3671
> Project: Atlas
> Issue Type: Bug
>Reporter: ygo
>Priority: Blocker
> Attachments: image-2020-03-20-12-23-10-166.png,
> image-2020-03-20-12-23-26-760.png, image-2020-03-20-12-25-19-822.png,
> image-2020-03-20-12-26-08-408.png
>
>
> mvn clean -DskipTests package -Pdist,embedded-hbase-solr
>
> i try mvn package, but failed.
> mvn version : 3.6.1
>
>
> *first*. JanusGraph DB Impl 2.0.0 build failure.
> "com.sleepycat:je:pom:7.4.5" in "http://repo1.maven.org/maven2;
> !image-2020-03-20-12-23-10-166.png|width=833,height=68!
> !image-2020-03-20-12-23-26-760.png|width=1344,height=45!
> * i modified the pom.xml file
> **
> oracleReleases
> Oracle Released Java Packages
> [http://download.oracle.com/maven]
> default
>
>
> *second.* Storm bridge shim 2.0.0 build failure.
> !image-2020-03-20-12-25-19-822.png|width=589,height=236!
> !image-2020-03-20-12-26-08-408.png|width=1217,height=40!
>
> * i modified the pom.xml file
> **
> atlassian-public
> https://maven.atlassian.com/repository/public
>
> true
> never
> warn
>
>
> true
> warn
>
>
>
> *result. build succeed*
>
> Did I do something wrong? Otherwise, please modify the source.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4729: --- Attachment: image-2023-02-14-17-05-15-213.png > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png, > image-2023-02-14-17-05-15-213.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688467#comment-17688467 ] Nixon Rodrigues commented on ATLAS-4729: !image-2023-02-14-17-05-15-213.png! > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png, > image-2023-02-14-17-05-15-213.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4729: --- Attachment: image-2023-02-14-17-04-26-576.png > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729 ] Nixon Rodrigues deleted comment on ATLAS-4729: was (Author: nixonrodrigues): !image-2023-02-14-17-04-26-576.png! > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688466#comment-17688466 ] Nixon Rodrigues commented on ATLAS-4729: !image-2023-02-14-17-04-26-576.png! > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > Attachments: image-2023-02-14-17-04-26-576.png > > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4729: --- Attachment: image (31).png > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
[ https://issues.apache.org/jira/browse/ATLAS-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-4729: --- Attachment: (was: image (31).png) > create entity fails if enum with name "date" or "int" is created. > -- > > Key: ATLAS-4729 > URL: https://issues.apache.org/jira/browse/ATLAS-4729 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Nixon Rodrigues >Priority: Minor > > create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4729) create entity fails if enum with name "date" or "int" is created.
Nixon Rodrigues created ATLAS-4729: -- Summary: create entity fails if enum with name "date" or "int" is created. Key: ATLAS-4729 URL: https://issues.apache.org/jira/browse/ATLAS-4729 Project: Atlas Issue Type: Bug Components: atlas-core Reporter: Nixon Rodrigues create entity fails if enum with name "date" or "int" is created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4576) Backward compatibility for check provided for AttributeName in Parent and Child TypeDef
[ https://issues.apache.org/jira/browse/ATLAS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687006#comment-17687006 ] ASF subversion and git services commented on ATLAS-4576: Commit eff7880f4528b3eecf4940f62fbe515d933e836b in atlas's branch refs/heads/dependabot/maven/graphdb/common/org.testng-testng-7.7.0 from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=eff7880f4 ] ATLAS-4576 Backward compatibility for check provided for AttributeName in Parent and Child TypeDef Signed-off-by: Mandar Ambawane > Backward compatibility for check provided for AttributeName in Parent and > Child TypeDef > --- > > Key: ATLAS-4576 > URL: https://issues.apache.org/jira/browse/ATLAS-4576 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Currently we have provided 2 checks for the Attribute Name: > [ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872] > Restrict typedef creation when a child type attribute conflicts with parent > type attribute of same name > [ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522] > Updating typedef with new supertype should be allowed only if attributes are > unique compared to other existing supertypes > But in the earlier versions these checks were not there. So there may be a > chance of Atlas environment having such data where these checks can cause > problems at the time: > 1. Atlas Startup. > 2. Creating new typedefs > This patch handles these scenarios and provides backward compatibility for > these 2 changes mentioned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4728) Atlas - Upgrade tinkerpop to 3.5.4
[ https://issues.apache.org/jira/browse/ATLAS-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687005#comment-17687005 ] ASF subversion and git services commented on ATLAS-4728: Commit b8c9816fee6278248f8019d7c53fa10adb053cb8 in atlas's branch refs/heads/branch-2.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=b8c9816fe ] ATLAS-4728: Upgrade tinkerpop to 3.5.4 Signed-off-by: Pinal Shah (cherry picked from commit 2989e4c265c54eb5aa5cc3837e7742af578139eb) > Atlas - Upgrade tinkerpop to 3.5.4 > -- > > Key: ATLAS-4728 > URL: https://issues.apache.org/jira/browse/ATLAS-4728 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Currently Atlas is using tinker pop version 3.5.2 upgrading it to 3.5.4 > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4728) Atlas - Upgrade tinkerpop to 3.5.4
[ https://issues.apache.org/jira/browse/ATLAS-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687007#comment-17687007 ] ASF subversion and git services commented on ATLAS-4728: Commit 2989e4c265c54eb5aa5cc3837e7742af578139eb in atlas's branch refs/heads/dependabot/maven/graphdb/common/org.testng-testng-7.7.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2989e4c26 ] ATLAS-4728: Upgrade tinkerpop to 3.5.4 Signed-off-by: Pinal Shah > Atlas - Upgrade tinkerpop to 3.5.4 > -- > > Key: ATLAS-4728 > URL: https://issues.apache.org/jira/browse/ATLAS-4728 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Currently Atlas is using tinker pop version 3.5.2 upgrading it to 3.5.4 > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4728) Atlas - Upgrade tinkerpop to 3.5.4
[ https://issues.apache.org/jira/browse/ATLAS-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687004#comment-17687004 ] ASF subversion and git services commented on ATLAS-4728: Commit 2989e4c265c54eb5aa5cc3837e7742af578139eb in atlas's branch refs/heads/master from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=2989e4c26 ] ATLAS-4728: Upgrade tinkerpop to 3.5.4 Signed-off-by: Pinal Shah > Atlas - Upgrade tinkerpop to 3.5.4 > -- > > Key: ATLAS-4728 > URL: https://issues.apache.org/jira/browse/ATLAS-4728 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Currently Atlas is using tinker pop version 3.5.2 upgrading it to 3.5.4 > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4719) Atlas - Upgrade Swagger to the latest version.
[ https://issues.apache.org/jira/browse/ATLAS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad P. Pawar resolved ATLAS-4719. Resolution: Fixed > Atlas - Upgrade Swagger to the latest version. > -- > > Key: ATLAS-4719 > URL: https://issues.apache.org/jira/browse/ATLAS-4719 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Prasad P. Pawar >Assignee: Prasad P. Pawar >Priority: Major > Attachments: > 0001-ATLAS-4719-UI-Upgrade-Swagger-to-the-latest-version.patch > > > Please upgrade this package to the latest version -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4728) Atlas - Upgrade tinkerpop to 3.5.4
[ https://issues.apache.org/jira/browse/ATLAS-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] VINAYAK MARRAIYA updated ATLAS-4728: Affects Version/s: 2.3.0 3.0.0 > Atlas - Upgrade tinkerpop to 3.5.4 > -- > > Key: ATLAS-4728 > URL: https://issues.apache.org/jira/browse/ATLAS-4728 > Project: Atlas > Issue Type: Improvement >Affects Versions: 3.0.0, 2.3.0 >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Currently Atlas is using tinker pop version 3.5.2 upgrading it to 3.5.4 > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ATLAS-4728) Atlas - Upgrade tinkerpop to 3.5.4
VINAYAK MARRAIYA created ATLAS-4728: --- Summary: Atlas - Upgrade tinkerpop to 3.5.4 Key: ATLAS-4728 URL: https://issues.apache.org/jira/browse/ATLAS-4728 Project: Atlas Issue Type: Improvement Reporter: VINAYAK MARRAIYA Currently Atlas is using tinker pop version 3.5.2 upgrading it to 3.5.4 h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4728) Atlas - Upgrade tinkerpop to 3.5.4
[ https://issues.apache.org/jira/browse/ATLAS-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] VINAYAK MARRAIYA reassigned ATLAS-4728: --- Assignee: VINAYAK MARRAIYA > Atlas - Upgrade tinkerpop to 3.5.4 > -- > > Key: ATLAS-4728 > URL: https://issues.apache.org/jira/browse/ATLAS-4728 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Currently Atlas is using tinker pop version 3.5.2 upgrading it to 3.5.4 > h4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-4576) Backward compatibility for check provided for AttributeName in Parent and Child TypeDef
[ https://issues.apache.org/jira/browse/ATLAS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandar Ambawane resolved ATLAS-4576. Resolution: Fixed > Backward compatibility for check provided for AttributeName in Parent and > Child TypeDef > --- > > Key: ATLAS-4576 > URL: https://issues.apache.org/jira/browse/ATLAS-4576 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Currently we have provided 2 checks for the Attribute Name: > [ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872] > Restrict typedef creation when a child type attribute conflicts with parent > type attribute of same name > [ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522] > Updating typedef with new supertype should be allowed only if attributes are > unique compared to other existing supertypes > But in the earlier versions these checks were not there. So there may be a > chance of Atlas environment having such data where these checks can cause > problems at the time: > 1. Atlas Startup. > 2. Creating new typedefs > This patch handles these scenarios and provides backward compatibility for > these 2 changes mentioned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4576) Backward compatibility for check provided for AttributeName in Parent and Child TypeDef
[ https://issues.apache.org/jira/browse/ATLAS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681249#comment-17681249 ] ASF subversion and git services commented on ATLAS-4576: Commit a3636b430b19320dedf684d89331738cb5213bd0 in atlas's branch refs/heads/branch-2.0 from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=a3636b430 ] ATLAS-4576 Backward compatibility for check provided for AttributeName in Parent and Child TypeDef Signed-off-by: Mandar Ambawane > Backward compatibility for check provided for AttributeName in Parent and > Child TypeDef > --- > > Key: ATLAS-4576 > URL: https://issues.apache.org/jira/browse/ATLAS-4576 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Currently we have provided 2 checks for the Attribute Name: > [ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872] > Restrict typedef creation when a child type attribute conflicts with parent > type attribute of same name > [ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522] > Updating typedef with new supertype should be allowed only if attributes are > unique compared to other existing supertypes > But in the earlier versions these checks were not there. So there may be a > chance of Atlas environment having such data where these checks can cause > problems at the time: > 1. Atlas Startup. > 2. Creating new typedefs > This patch handles these scenarios and provides backward compatibility for > these 2 changes mentioned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4576) Backward compatibility for check provided for AttributeName in Parent and Child TypeDef
[ https://issues.apache.org/jira/browse/ATLAS-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681202#comment-17681202 ] ASF subversion and git services commented on ATLAS-4576: Commit eff7880f4528b3eecf4940f62fbe515d933e836b in atlas's branch refs/heads/master from Mandar Ambawane [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=eff7880f4 ] ATLAS-4576 Backward compatibility for check provided for AttributeName in Parent and Child TypeDef Signed-off-by: Mandar Ambawane > Backward compatibility for check provided for AttributeName in Parent and > Child TypeDef > --- > > Key: ATLAS-4576 > URL: https://issues.apache.org/jira/browse/ATLAS-4576 > Project: Atlas > Issue Type: Improvement >Reporter: Mandar Ambawane >Assignee: Mandar Ambawane >Priority: Major > > Currently we have provided 2 checks for the Attribute Name: > [ATLAS-3872|https://issues.apache.org/jira/browse/ATLAS-3872] > Restrict typedef creation when a child type attribute conflicts with parent > type attribute of same name > [ATLAS-4522|https://issues.apache.org/jira/browse/ATLAS-4522] > Updating typedef with new supertype should be allowed only if attributes are > unique compared to other existing supertypes > But in the earlier versions these checks were not there. So there may be a > chance of Atlas environment having such data where these checks can cause > problems at the time: > 1. Atlas Startup. > 2. Creating new typedefs > This patch handles these scenarios and provides backward compatibility for > these 2 changes mentioned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-3756) Error when compile from source code - can not find restlet for transitive dep
[ https://issues.apache.org/jira/browse/ATLAS-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681114#comment-17681114 ] Madhan Neethiraj commented on ATLAS-3756: - [~hsaputra] - thank you for the fix. [~mcbeelen] - thank you for the nudge to get this fix merged. > Error when compile from source code - can not find restlet for transitive dep > - > > Key: ATLAS-3756 > URL: https://issues.apache.org/jira/browse/ATLAS-3756 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Henry Saputra >Assignee: Henry Saputra >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > When trying to compile Apache Atlas from code, got this error messages: > > mvn clean -DskipTests install > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 8.214 s > [INFO] Finished at: 2020-04-26T01:25:17-07:00 > [INFO] > > [ERROR] Failed to execute goal on project atlas-testtools: Could not resolve > dependencies for project org.apache.atlas:atlas-testtools:jar:3.0.0-SNAPSHOT: > The following artifacts could not be resolved: > org.restlet.jee:org.restlet:jar:2.3.0, > org.restlet.jee:org.restlet.ext.servlet:jar:2.3.0: Failure to find > org.restlet.jee:org.restlet:jar:2.3.0 in https://repo1.maven.org/maven2 was > cached in the local repository, resolution will not be reattempted until the > update interval of central has elapsed or updates are forced -> [Help 1] > > Maven version: > 3.6.3 > > Java version: > OpenJDK 1.8.0 - 252 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (ATLAS-3756) Error when compile from source code - can not find restlet for transitive dep
[ https://issues.apache.org/jira/browse/ATLAS-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved ATLAS-3756. - Fix Version/s: 2.4.0 3.0.0 Resolution: Fixed > Error when compile from source code - can not find restlet for transitive dep > - > > Key: ATLAS-3756 > URL: https://issues.apache.org/jira/browse/ATLAS-3756 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Henry Saputra >Assignee: Henry Saputra >Priority: Major > Fix For: 3.0.0, 2.4.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When trying to compile Apache Atlas from code, got this error messages: > > mvn clean -DskipTests install > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 8.214 s > [INFO] Finished at: 2020-04-26T01:25:17-07:00 > [INFO] > > [ERROR] Failed to execute goal on project atlas-testtools: Could not resolve > dependencies for project org.apache.atlas:atlas-testtools:jar:3.0.0-SNAPSHOT: > The following artifacts could not be resolved: > org.restlet.jee:org.restlet:jar:2.3.0, > org.restlet.jee:org.restlet.ext.servlet:jar:2.3.0: Failure to find > org.restlet.jee:org.restlet:jar:2.3.0 in https://repo1.maven.org/maven2 was > cached in the local repository, resolution will not be reattempted until the > update interval of central has elapsed or updates are forced -> [Help 1] > > Maven version: > 3.6.3 > > Java version: > OpenJDK 1.8.0 - 252 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-3756) Error when compile from source code - can not find restlet for transitive dep
[ https://issues.apache.org/jira/browse/ATLAS-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj reassigned ATLAS-3756: --- Assignee: Henry Saputra > Error when compile from source code - can not find restlet for transitive dep > - > > Key: ATLAS-3756 > URL: https://issues.apache.org/jira/browse/ATLAS-3756 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Henry Saputra >Assignee: Henry Saputra >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > When trying to compile Apache Atlas from code, got this error messages: > > mvn clean -DskipTests install > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 8.214 s > [INFO] Finished at: 2020-04-26T01:25:17-07:00 > [INFO] > > [ERROR] Failed to execute goal on project atlas-testtools: Could not resolve > dependencies for project org.apache.atlas:atlas-testtools:jar:3.0.0-SNAPSHOT: > The following artifacts could not be resolved: > org.restlet.jee:org.restlet:jar:2.3.0, > org.restlet.jee:org.restlet.ext.servlet:jar:2.3.0: Failure to find > org.restlet.jee:org.restlet:jar:2.3.0 in https://repo1.maven.org/maven2 was > cached in the local repository, resolution will not be reattempted until the > update interval of central has elapsed or updates are forced -> [Help 1] > > Maven version: > 3.6.3 > > Java version: > OpenJDK 1.8.0 - 252 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-3756) Error when compile from source code - can not find restlet for transitive dep
[ https://issues.apache.org/jira/browse/ATLAS-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681113#comment-17681113 ] ASF subversion and git services commented on ATLAS-3756: Commit 9b527dd4974a317383ef81cf9de7d140ea064480 in atlas's branch refs/heads/branch-2.0 from Henry Saputra [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9b527dd49 ] ATLAS-3756: fixed build error due to restlet library dependency resolution Signed-off-by: Madhan Neethiraj (cherry picked from commit d1781a7c38e2da24cb023588dc91ef88b5cbb067) > Error when compile from source code - can not find restlet for transitive dep > - > > Key: ATLAS-3756 > URL: https://issues.apache.org/jira/browse/ATLAS-3756 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Henry Saputra >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When trying to compile Apache Atlas from code, got this error messages: > > mvn clean -DskipTests install > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 8.214 s > [INFO] Finished at: 2020-04-26T01:25:17-07:00 > [INFO] > > [ERROR] Failed to execute goal on project atlas-testtools: Could not resolve > dependencies for project org.apache.atlas:atlas-testtools:jar:3.0.0-SNAPSHOT: > The following artifacts could not be resolved: > org.restlet.jee:org.restlet:jar:2.3.0, > org.restlet.jee:org.restlet.ext.servlet:jar:2.3.0: Failure to find > org.restlet.jee:org.restlet:jar:2.3.0 in https://repo1.maven.org/maven2 was > cached in the local repository, resolution will not be reattempted until the > update interval of central has elapsed or updates are forced -> [Help 1] > > Maven version: > 3.6.3 > > Java version: > OpenJDK 1.8.0 - 252 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-3756) Error when compile from source code - can not find restlet for transitive dep
[ https://issues.apache.org/jira/browse/ATLAS-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681112#comment-17681112 ] ASF subversion and git services commented on ATLAS-3756: Commit d1781a7c38e2da24cb023588dc91ef88b5cbb067 in atlas's branch refs/heads/master from Henry Saputra [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d1781a7c3 ] ATLAS-3756: fixed build error due to restlet library dependency resolution Signed-off-by: Madhan Neethiraj > Error when compile from source code - can not find restlet for transitive dep > - > > Key: ATLAS-3756 > URL: https://issues.apache.org/jira/browse/ATLAS-3756 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Henry Saputra >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When trying to compile Apache Atlas from code, got this error messages: > > mvn clean -DskipTests install > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 8.214 s > [INFO] Finished at: 2020-04-26T01:25:17-07:00 > [INFO] > > [ERROR] Failed to execute goal on project atlas-testtools: Could not resolve > dependencies for project org.apache.atlas:atlas-testtools:jar:3.0.0-SNAPSHOT: > The following artifacts could not be resolved: > org.restlet.jee:org.restlet:jar:2.3.0, > org.restlet.jee:org.restlet.ext.servlet:jar:2.3.0: Failure to find > org.restlet.jee:org.restlet:jar:2.3.0 in https://repo1.maven.org/maven2 was > cached in the local repository, resolution will not be reattempted until the > update interval of central has elapsed or updates are forced -> [Help 1] > > Maven version: > 3.6.3 > > Java version: > OpenJDK 1.8.0 - 252 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-3756) Error when compile from source code - can not find restlet for transitive dep
[ https://issues.apache.org/jira/browse/ATLAS-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17680937#comment-17680937 ] Marco Beelen commented on ATLAS-3756: - I noticed this issue as well and wanted to create an issue for it, but already found this existing one. There is already a PR to fix this ([https://github.com/apache/atlas/pull/96]) and a duplicate PR ([https://github.com/apache/atlas/pull/219]). That make me at least the 3rd person to run into this issue. @ [~VinayakMarraiya] : I noticed you committed some small changes to the pom in the last couple of weeks, perhaps include this in the clean up? > Error when compile from source code - can not find restlet for transitive dep > - > > Key: ATLAS-3756 > URL: https://issues.apache.org/jira/browse/ATLAS-3756 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 3.0.0 >Reporter: Henry Saputra >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When trying to compile Apache Atlas from code, got this error messages: > > mvn clean -DskipTests install > > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 8.214 s > [INFO] Finished at: 2020-04-26T01:25:17-07:00 > [INFO] > > [ERROR] Failed to execute goal on project atlas-testtools: Could not resolve > dependencies for project org.apache.atlas:atlas-testtools:jar:3.0.0-SNAPSHOT: > The following artifacts could not be resolved: > org.restlet.jee:org.restlet:jar:2.3.0, > org.restlet.jee:org.restlet.ext.servlet:jar:2.3.0: Failure to find > org.restlet.jee:org.restlet:jar:2.3.0 in https://repo1.maven.org/maven2 was > cached in the local repository, resolution will not be reattempted until the > update interval of central has elapsed or updates are forced -> [Help 1] > > Maven version: > 3.6.3 > > Java version: > OpenJDK 1.8.0 - 252 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ATLAS-4725) UI (Swagger): API request not being fired correctly for uniqueAttribute related EntityREST APIs
[
https://issues.apache.org/jira/browse/ATLAS-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Farhan Khan updated ATLAS-4725:
---
Attachment: 0001-ATLAS-4725-UI-Swagger-API-request-not-being-fired-co.patch
> UI (Swagger): API request not being fired correctly for uniqueAttribute
> related EntityREST APIs
> ---
>
> Key: ATLAS-4725
> URL: https://issues.apache.org/jira/browse/ATLAS-4725
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Farhan Khan
>Priority: Minor
> Attachments:
> 0001-ATLAS-4725-UI-Swagger-API-request-not-being-fired-co.patch
>
>
> There are two issues in the EntityREST APIs section in the Swagger UI given
> under the API Documentation link.
> 1. The APIs are not sanitized properly when fired from the Swagger API page
> and always throws an error. It occurs in the following uniqueAttribute
> related APIs:
> DELETE /v2/entity/uniqueAttribute/type/\{typeName}
>
> GET /v2/entity/uniqueAttribute/type/\{typeName}
>
> PUT /v2/entity/uniqueAttribute/type/\{typeName}
>
> DELETE
> /v2/entity/uniqueAttribute/type/\{typeName}/classification/\{classificationName}
>
>
> POST /v2/entity/uniqueAttribute/type/\{typeName}/classifications
>
> PUT /v2/entity/uniqueAttribute/type/\{typeName}/classifications
>
> GET /v2/entity/uniqueAttribute/type/\{typeName}/header
>
> DELETE /v2/entity/uniqueAttribute/type/\{typeName}/labels
>
> POST /v2/entity/uniqueAttribute/type/\{typeName}/labels
>
> PUT /v2/entity/uniqueAttribute/type/\{typeName}/labels
> 2. It is not possible to pass a valid request to these APIs in the API page:
> /v2/entity/uniqueAttribute/type/\{typeName}/classification/\{classificationName}
>
>
> /v2/entity/uniqueAttribute/type/\{typeName}/classifications
>
> /v2/entity/uniqueAttribute/type/\{typeName}/classifications
>
> /v2/entity/uniqueAttribute/type/\{typeName}/header
>
> /v2/entity/uniqueAttribute/type/\{typeName}/labels
> This is because the property attribute and value is improperly added in the
> wrong position in the header for these APIs when the request is fired from
> the API page.
> The positioning of the key-value pair has to be fixed, and it would be better
> to have a dedicated field for specifying the property name and value for the
> uniqueAttribute APIs.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4727) admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is not indexed in the targeted index [vertex_index]'
[
https://issues.apache.org/jira/browse/ATLAS-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4727:
--
Fix Version/s: 3.0.0
> admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is
> not indexed in the targeted index [vertex_index]'
> -
>
> Key: ATLAS-4727
> URL: https://issues.apache.org/jira/browse/ATLAS-4727
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
>
> Issue:
> admin/audits , admin/purge calls throw 500 internal server error.
> Error:
> {code:java}
> java.lang.IllegalArgumentException: The used key
> [__AtlasAuditEntry.startTime] is not indexed in the targeted index
> [vertex_index] at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:435)
> at
> org.janusgraph.graphdb.database.IndexSerializer.getOrders(IndexSerializer.java:711)
> at
> org.janusgraph.graphdb.database.IndexSerializer.executeQuery(IndexSerializer.java:726){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (ATLAS-4727) admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is not indexed in the targeted index [vertex_index]'
[
https://issues.apache.org/jira/browse/ATLAS-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinal Shah updated ATLAS-4727:
--
Fix Version/s: 2.4.0
> admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is
> not indexed in the targeted index [vertex_index]'
> -
>
> Key: ATLAS-4727
> URL: https://issues.apache.org/jira/browse/ATLAS-4727
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
> Fix For: 2.4.0
>
>
> Issue:
> admin/audits , admin/purge calls throw 500 internal server error.
> Error:
> {code:java}
> java.lang.IllegalArgumentException: The used key
> [__AtlasAuditEntry.startTime] is not indexed in the targeted index
> [vertex_index] at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:435)
> at
> org.janusgraph.graphdb.database.IndexSerializer.getOrders(IndexSerializer.java:711)
> at
> org.janusgraph.graphdb.database.IndexSerializer.executeQuery(IndexSerializer.java:726){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4727) admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is not indexed in the targeted index [vertex_index]'
[
https://issues.apache.org/jira/browse/ATLAS-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17679666#comment-17679666
]
ASF subversion and git services commented on ATLAS-4727:
Commit 8ded492ad4e391de62278007281ef5121b6cc497 in atlas's branch
refs/heads/branch-2.0 from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8ded492ad ]
ATLAS-4727: admin/audits , admin/purge APIs fail with
'[__AtlasAuditEntry.startTime] is not indexed in the targeted index
[vertex_index]'
Signed-off-by: Pinal Shah
(cherry picked from commit 8c1b1430a1fe21c2dc8cf30c619f93411cdac628)
> admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is
> not indexed in the targeted index [vertex_index]'
> -
>
> Key: ATLAS-4727
> URL: https://issues.apache.org/jira/browse/ATLAS-4727
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>
> Issue:
> admin/audits , admin/purge calls throw 500 internal server error.
> Error:
> {code:java}
> java.lang.IllegalArgumentException: The used key
> [__AtlasAuditEntry.startTime] is not indexed in the targeted index
> [vertex_index] at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:435)
> at
> org.janusgraph.graphdb.database.IndexSerializer.getOrders(IndexSerializer.java:711)
> at
> org.janusgraph.graphdb.database.IndexSerializer.executeQuery(IndexSerializer.java:726){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4727) admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is not indexed in the targeted index [vertex_index]'
[
https://issues.apache.org/jira/browse/ATLAS-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17679665#comment-17679665
]
ASF subversion and git services commented on ATLAS-4727:
Commit 8c1b1430a1fe21c2dc8cf30c619f93411cdac628 in atlas's branch
refs/heads/master from Pinal Shah
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=8c1b1430a ]
ATLAS-4727: admin/audits , admin/purge APIs fail with
'[__AtlasAuditEntry.startTime] is not indexed in the targeted index
[vertex_index]'
Signed-off-by: Pinal Shah
> admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is
> not indexed in the targeted index [vertex_index]'
> -
>
> Key: ATLAS-4727
> URL: https://issues.apache.org/jira/browse/ATLAS-4727
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
>Reporter: Pinal Shah
>Assignee: Pinal Shah
>Priority: Major
>
> Issue:
> admin/audits , admin/purge calls throw 500 internal server error.
> Error:
> {code:java}
> java.lang.IllegalArgumentException: The used key
> [__AtlasAuditEntry.startTime] is not indexed in the targeted index
> [vertex_index] at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:435)
> at
> org.janusgraph.graphdb.database.IndexSerializer.getOrders(IndexSerializer.java:711)
> at
> org.janusgraph.graphdb.database.IndexSerializer.executeQuery(IndexSerializer.java:726){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4727) admin/audits , admin/purge APIs fail with '[__AtlasAuditEntry.startTime] is not indexed in the targeted index [vertex_index]'
Pinal Shah created ATLAS-4727:
-
Summary: admin/audits , admin/purge APIs fail with
'[__AtlasAuditEntry.startTime] is not indexed in the targeted index
[vertex_index]'
Key: ATLAS-4727
URL: https://issues.apache.org/jira/browse/ATLAS-4727
Project: Atlas
Issue Type: Bug
Components: atlas-core
Reporter: Pinal Shah
Assignee: Pinal Shah
Issue:
admin/audits , admin/purge calls throw 500 internal server error.
Error:
{code:java}
java.lang.IllegalArgumentException: The used key [__AtlasAuditEntry.startTime]
is not indexed in the targeted index [vertex_index] at
com.google.common.base.Preconditions.checkArgument(Preconditions.java:435)
at
org.janusgraph.graphdb.database.IndexSerializer.getOrders(IndexSerializer.java:711)
at
org.janusgraph.graphdb.database.IndexSerializer.executeQuery(IndexSerializer.java:726){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ATLAS-4726) Irregular "Error Details" format when there is an Error in Bulk Import Business Metadata
Umesh Padashetty created ATLAS-4726:
---
Summary: Irregular "Error Details" format when there is an Error
in Bulk Import Business Metadata
Key: ATLAS-4726
URL: https://issues.apache.org/jira/browse/ATLAS-4726
Project: Atlas
Issue Type: Bug
Reporter: Umesh Padashetty
Attachments: Screenshot 2023-01-17 at 10.30.22 PM.png, Screenshot
2023-01-17 at 10.31.13 PM.png
Attached screenshots, you can see that we are printing Error details in
different formats
In some cases we print
* Provided value PURGE is Enumeration of Long type at line #20
In other cases we print
* Line #2: invalid business-metadata 'BM2.A1' for entity type 'hive_table'
I think it is a good idea to maintain the following format to increase the
readability of error
: Error like below
{code:java}
Line #2: invalid business-metadata 'BM2.A1' for entity type 'hive_table'
Line #3: invalid business-metadata 'BM2.A3' for entity type 'hive_table'
Line #4: invalid business-metadata 'BM2.A5' for entity type 'hive_table'
Line #5: invalid business-metadata 'BM2.A7' for entity type 'hive_table'
Line #6: invalid business-metadata 'BM2.A9' for entity type 'hive_table'
Line #7: invalid business-metadata 'BM2.A11' for entity type 'hive_table'
Line #8: invalid business-metadata 'BM2.A13' for entity type 'hive_table'
Line #9: invalid business-metadata 'BM2.A15' for entity type 'hive_table'
Line #10: invalid business-metadata 'BM2.A17' for entity type 'hive_table'
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ATLAS-4654) 'atlas.graph.index.search.max-result-set-size' doesn't map to a List object: 150
[
https://issues.apache.org/jira/browse/ATLAS-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677409#comment-17677409
]
Sheetal Shah commented on ATLAS-4654:
-
[~O.Tougui] , we ran the same sqoop import command mentioned in description and
it ran successfully without producing any errors.
Following are the application versions with which we tested:
• Sqoop 1.4.7
• Postgresql 12
• apache-atlas 2.3.0
• sqoop hook required
jar-atlas-plugin-classloader-3.0.0-SNAPSHOT.jar,atlas-sqoop-plugin-impl,sqoop-bridge-shim-3.0.0-SNAPSHOT.jar
The property value used in application.properties file to run this command:
{code:java}
# Solr-specific configuration property
atlas.graph.index.search.max-result-set-size=150 {code}
Stack-trace produced after running this command:
{code:java}
2023-01-12 09:46:39,755 INFO mapreduce.ImportJobBase: Transferred 0 bytes in
2.2808 seconds (0 bytes/sec)
2023-01-12 09:46:39,756 INFO mapreduce.ImportJobBase: Retrieved 0 records.
2023-01-12 09:46:39,756 INFO mapreduce.ImportJobBase: Publishing Hive/Hcat
import job data to Listeners for table supplies
2023-01-12 09:46:39,842 INFO atlas.ApplicationProperties: Looking for
atlas-application.properties in classpath
2023-01-12 09:46:39,843 INFO atlas.ApplicationProperties: Loading
atlas-application.properties from
file:/usr/lib/sqoop-1.4.7.bin__hadoop-2.6.0/conf/atlas-application.properties
2023-01-12 09:46:39,883 INFO atlas.ApplicationProperties: Using graphdb backend
'janus'
2023-01-12 09:46:39,883 INFO atlas.ApplicationProperties: Using storage backend
'hbase2'
2023-01-12 09:46:39,883 INFO atlas.ApplicationProperties: Using index backend
'solr5'
2023-01-12 09:46:39,883 INFO atlas.ApplicationProperties: Setting
atlas.graph.index.search.max-result-set-size = 150
2023-01-12 09:46:39,885 INFO atlas.ApplicationProperties: Setting
atlas.graph.index.search.solr.wait-searcher = false
2023-01-12 09:46:40,540 INFO notification.LogConfigUtils: Could not infer log
path from this appender: org.apache.logging.log4j.core.appender.ConsoleAppender
2023-01-12 09:46:40,540 INFO notification.LogConfigUtils:
getFileAppenderPath(): ret=
2023-01-12 09:46:40,541 INFO notification.LogConfigUtils:
getFileAppenderPathApproach2(): ret=
2023-01-12 09:46:40,541 INFO notification.LogConfigUtils: getRootDir(): ret=null
{code}
Kindly share your atlas-application.properties file and versions of
applications that you are using.
CC : [~jayendrap]
> 'atlas.graph.index.search.max-result-set-size' doesn't map to a List object:
> 150
>
>
> Key: ATLAS-4654
> URL: https://issues.apache.org/jira/browse/ATLAS-4654
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
>Affects Versions: 2.3.0
>Reporter: Omar Tougui
>Priority: Blocker
>
> when I run the following sqoop command :
>
>
> {{sqoop import --connect jdbc:postgresql://server/db --username user -P
> --table tab --hive-import --create-hive-table}}
> {{}}
> {{I get this error:}}
> {{}}
>
> {{{}22/08/01 16:44:51 INFO atlas.ApplicationProperties: Setting
> atlas.graph.index.search.max-result-set-size = 150
> 22/08/01 16:44:51 INFO atlas.ApplicationProperties: Setting
> atlas.graph.index.search.solr.wait-searcher = false
> 22/08/01 16:44:51 INFO atlas.ApplicationProperties: Property (set to default)
> atlas.graph.cache.db-cache = true
> 22/08/01 16:44:51 INFO atlas.ApplicationProperties: Property (set to default)
> atlas.graph.cache.db-cache-clean-wait = 20
> 22/08/01 16:44:51 INFO atlas.ApplicationProperties: Property (set to default)
> atlas.graph.cache.db-cache-size = 0.5
> 22/08/01 16:44:51 INFO atlas.ApplicationProperties: Property (set to default)
> atlas.graph.cache.tx-cache-size = 15000
> 22/08/01 16:44:51 INFO atlas.ApplicationProperties: Property (set to default)
> atlas.graph.cache.tx-dirty-size = 120
> 22/08/01 16:44:51 INFO hook.AtlasHook: Failed to load application properties
> org.apache.atlas.AtlasException: Failed to load application properties
> at
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:155)
> at
> org.apache.atlas.ApplicationProperties.get(ApplicationProperties.java:108)
> at org.apache.atlas.hook.AtlasHook.(AtlasHook.java:82)
> at org.apache.atlas.sqoop.hook.SqoopHook.(SqoopHook.java:86)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.sqoop.mapreduce.PublishJobData.publishJobData(PublishJobData.java:46)
> at
> org.apache.sqoop.mapreduce.ImportJobBase.runImport(ImportJobBase.java:284)
>
[jira] [Commented] (ATLAS-4723) Atlas - Upgrade snakeyaml to 1.33
[ https://issues.apache.org/jira/browse/ATLAS-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677170#comment-17677170 ] ASF subversion and git services commented on ATLAS-4723: Commit 4c230e78e2f33be0ba38da7797a6600cacbe2820 in atlas's branch refs/heads/branch-2.0 from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4c230e78e ] ATLAS-4723 : Upgrade snakeyaml to 1.33 Signed-off-by: Pinal Shah (cherry picked from commit bb656e41f90f278426068b571c92fe3bb772492f) > Atlas - Upgrade snakeyaml to 1.33 > - > > Key: ATLAS-4723 > URL: https://issues.apache.org/jira/browse/ATLAS-4723 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Currently Atlas is using snakeyaml version 1.32 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ATLAS-4723) Atlas - Upgrade snakeyaml to 1.33
[ https://issues.apache.org/jira/browse/ATLAS-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677169#comment-17677169 ] ASF subversion and git services commented on ATLAS-4723: Commit bb656e41f90f278426068b571c92fe3bb772492f in atlas's branch refs/heads/master from vinayak.marraiya [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=bb656e41f ] ATLAS-4723 : Upgrade snakeyaml to 1.33 Signed-off-by: Pinal Shah > Atlas - Upgrade snakeyaml to 1.33 > - > > Key: ATLAS-4723 > URL: https://issues.apache.org/jira/browse/ATLAS-4723 > Project: Atlas > Issue Type: Improvement >Reporter: VINAYAK MARRAIYA >Assignee: VINAYAK MARRAIYA >Priority: Major > > Currently Atlas is using snakeyaml version 1.32 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (ATLAS-4725) UI (Swagger): API request not being fired correctly for uniqueAttribute related EntityREST APIs
[
https://issues.apache.org/jira/browse/ATLAS-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Farhan Khan reassigned ATLAS-4725:
--
Assignee: Farhan Khan
> UI (Swagger): API request not being fired correctly for uniqueAttribute
> related EntityREST APIs
> ---
>
> Key: ATLAS-4725
> URL: https://issues.apache.org/jira/browse/ATLAS-4725
> Project: Atlas
> Issue Type: Bug
>Reporter: Rahul Kurup
>Assignee: Farhan Khan
>Priority: Minor
>
> There are two issues in the EntityREST APIs section in the Swagger UI given
> under the API Documentation link.
> 1. The APIs are not sanitized properly when fired from the Swagger API page
> and always throws an error. It occurs in the following uniqueAttribute
> related APIs:
> DELETE /v2/entity/uniqueAttribute/type/\{typeName}
>
> GET /v2/entity/uniqueAttribute/type/\{typeName}
>
> PUT /v2/entity/uniqueAttribute/type/\{typeName}
>
> DELETE
> /v2/entity/uniqueAttribute/type/\{typeName}/classification/\{classificationName}
>
>
> POST /v2/entity/uniqueAttribute/type/\{typeName}/classifications
>
> PUT /v2/entity/uniqueAttribute/type/\{typeName}/classifications
>
> GET /v2/entity/uniqueAttribute/type/\{typeName}/header
>
> DELETE /v2/entity/uniqueAttribute/type/\{typeName}/labels
>
> POST /v2/entity/uniqueAttribute/type/\{typeName}/labels
>
> PUT /v2/entity/uniqueAttribute/type/\{typeName}/labels
> 2. It is not possible to pass a valid request to these APIs in the API page:
> /v2/entity/uniqueAttribute/type/\{typeName}/classification/\{classificationName}
>
>
> /v2/entity/uniqueAttribute/type/\{typeName}/classifications
>
> /v2/entity/uniqueAttribute/type/\{typeName}/classifications
>
> /v2/entity/uniqueAttribute/type/\{typeName}/header
>
> /v2/entity/uniqueAttribute/type/\{typeName}/labels
> This is because the property attribute and value is improperly added in the
> wrong position in the header for these APIs when the request is fired from
> the API page.
> The positioning of the key-value pair has to be fixed, and it would be better
> to have a dedicated field for specifying the property name and value for the
> uniqueAttribute APIs.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
