Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move temporary importer data into a separate database #74

Open
mgrbyte opened this issue May 22, 2017 · 0 comments
Open

Move temporary importer data into a separate database #74

mgrbyte opened this issue May 22, 2017 · 0 comments
Assignees
Labels

Comments

@mgrbyte
Copy link
Contributor

mgrbyte commented May 22, 2017

The excise-tmp-data step is causing issues in the migration process - it never completes (in any timely fashion) due to the nature/misuse of datomic's excise API.

https://groups.google.com/forum/#!topic/datomic/0hN6cFZgqBo

The impoter namespace only contains two attributes:
temp - An identifier used as scaffolding by the timestamp-aware importer
ts-name - Username from legacy ACeDB timestamp

  • Create a temporary database that persists just for the life-time of the import process.
    (Deleting the database at the end of a migration run)
  • Remove the command from the CLI, and the corresponding step in the db-migration pipeline code.
@mgrbyte mgrbyte added the WS260 label May 22, 2017
@mgrbyte mgrbyte added this to the 0.5.2 milestone May 22, 2017
@mgrbyte mgrbyte self-assigned this May 22, 2017
@mgrbyte mgrbyte removed the WS260 label Jul 6, 2017
@mgrbyte mgrbyte removed this from the 0.5.2 milestone Sep 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant