[jira] [Updated] (ATLAS-3775) Migration Import Display: Incorrect Status Display
[ https://issues.apache.org/jira/browse/ATLAS-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated ATLAS-3775: Fix Version/s: (was: trunk) 3.0.0 2.1.0 > Migration Import Display: Incorrect Status Display > -- > > Key: ATLAS-3775 > URL: https://issues.apache.org/jira/browse/ATLAS-3775 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3775-Migration-Import-Status-display-fix.patch > > > *Background* > Zip file based migration introduced _DataMigrationStatusService_. This class > is responsible for displaying the status. > *Steps to Duplicate* > Pre-requisites: > * Keep the REST http:///api/atlas/admin output open in a browser > window. > * Keep zip-file based migration import in progress. > * Ensure that you see the current status. Once migration progress, refresh > the REST API output to display the status. The status should be accurate. > * Refresh the REST API output after 5 mins. This will expire the status > cache and make a request to _DataMigrationService_ for status. > _Expected results_ > * Status returned by API should reflect the status logged. > > _Actual results_ > * There is a mismatch in the status. > * Additional information: The status is never updated for that session. > Root cause: > - _DataMigrationService_ maintains cached status object for each requestor. > This is not refreshed from the database status. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3775) Migration Import Display: Incorrect Status Display
[ https://issues.apache.org/jira/browse/ATLAS-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3775: --- Attachment: (was: ATLAS-3775-Migration-Import-Status-display-fix.patch) > Migration Import Display: Incorrect Status Display > -- > > Key: ATLAS-3775 > URL: https://issues.apache.org/jira/browse/ATLAS-3775 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3775-Migration-Import-Status-display-fix.patch > > > *Background* > Zip file based migration introduced _DataMigrationStatusService_. This class > is responsible for displaying the status. > *Steps to Duplicate* > Pre-requisites: > * Keep the REST http:///api/atlas/admin output open in a browser > window. > * Keep zip-file based migration import in progress. > * Ensure that you see the current status. Once migration progress, refresh > the REST API output to display the status. The status should be accurate. > * Refresh the REST API output after 5 mins. This will expire the status > cache and make a request to _DataMigrationService_ for status. > _Expected results_ > * Status returned by API should reflect the status logged. > > _Actual results_ > * There is a mismatch in the status. > * Additional information: The status is never updated for that session. > Root cause: > - _DataMigrationService_ maintains cached status object for each requestor. > This is not refreshed from the database status. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3775) Migration Import Display: Incorrect Status Display
[ https://issues.apache.org/jira/browse/ATLAS-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3775: --- Attachment: ATLAS-3775-Migration-Import-Status-display-fix.patch > Migration Import Display: Incorrect Status Display > -- > > Key: ATLAS-3775 > URL: https://issues.apache.org/jira/browse/ATLAS-3775 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3775-Migration-Import-Status-display-fix.patch, > ATLAS-3775-Migration-Import-Status-display-fix.patch > > > *Background* > Zip file based migration introduced _DataMigrationStatusService_. This class > is responsible for displaying the status. > *Steps to Duplicate* > Pre-requisites: > * Keep the REST http:///api/atlas/admin output open in a browser > window. > * Keep zip-file based migration import in progress. > * Ensure that you see the current status. Once migration progress, refresh > the REST API output to display the status. The status should be accurate. > * Refresh the REST API output after 5 mins. This will expire the status > cache and make a request to _DataMigrationService_ for status. > _Expected results_ > * Status returned by API should reflect the status logged. > > _Actual results_ > * There is a mismatch in the status. > * Additional information: The status is never updated for that session. > Root cause: > - _DataMigrationService_ maintains cached status object for each requestor. > This is not refreshed from the database status. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3775) Migration Import Display: Incorrect Status Display
[ https://issues.apache.org/jira/browse/ATLAS-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3775: --- Attachment: ATLAS-3775-Migration-Import-Status-display-fix.patch > Migration Import Display: Incorrect Status Display > -- > > Key: ATLAS-3775 > URL: https://issues.apache.org/jira/browse/ATLAS-3775 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3775-Migration-Import-Status-display-fix.patch > > > *Background* > Zip file based migration introduced _DataMigrationStatusService_. This class > is responsible for displaying the status. > *Steps to Duplicate* > Pre-requisites: > * Keep the REST http:///api/atlas/admin output open in a browser > window. > * Keep zip-file based migration import in progress. > * Ensure that you see the current status. Once migration progress, refresh > the REST API output to display the status. The status should be accurate. > * Refresh the REST API output after 5 mins. This will expire the status > cache and make a request to _DataMigrationService_ for status. > _Expected results_ > * Status returned by API should reflect the status logged. > > _Actual results_ > * There is a mismatch in the status. > * Additional information: The status is never updated for that session. > Root cause: > - _DataMigrationService_ maintains cached status object for each requestor. > This is not refreshed from the database status. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
