[
https://issues.apache.org/jira/browse/ATLAS-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100059#comment-17100059
]
ASF subversion and git services commented on ATLAS-3775:
--------------------------------------------------------
Commit f467229294baa5550f4101d1e8ea59e82fdf3e3b in atlas's branch
refs/heads/master from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=f467229 ]
ATLAS-3775: Migration Import: Status display fix.
> 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://<server>/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)
