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

Read manifest from database #113

Closed
2 tasks
Tracked by #244 ...
sirex opened this issue Mar 19, 2021 · 1 comment · Fixed by #495
Closed
2 tasks
Tracked by #244 ...

Read manifest from database #113

sirex opened this issue Mar 19, 2021 · 1 comment · Fixed by #495

Comments

@sirex
Copy link
Collaborator

sirex commented Mar 19, 2021

Currently we have a manifest called backend, which allows to read and store manifest in database, using any backend. Current implementation is too complicated and should be simplified.

Current implementation allows to use any existing backend, to store manifest, but this complicates thing and we should support only sqlalchemy backend, which should simplify things a lot. This new manifest should be called internal.

This manifest should work as a normal manifest, it should support usual things, other manifests support, for example:

spinta show
spinta copy manifest.csv -o postgresql://host/db
spinta copy postgresql://host/db -o manifest.csv
spinta run

One major difference, that sqlalchemy manifest, should support reading schema on demand, model by model. For example if someone requests data of /example/dataset/MyModel, then on request, only schema of this model should be read. This would allow to have large manifests and make it possible to have a dynamic schema updates, because schema would be stored in database and it would be read every time on request.

There is one issue, that models can have dependencies, so it should be possible to dynamically load parts of schema as they are needed.

Tasks

@sirex
Copy link
Collaborator Author

sirex commented Mar 19, 2021

marked this issue as related to #64

@sirex sirex removed the epic label May 24, 2022
@sirex sirex changed the title Schema migration via API Read manifest from database Jun 14, 2023
@adp-atea adp-atea moved this to In Progress in Portalo plėtra Jul 18, 2023
@adp-atea adp-atea linked a pull request Jul 24, 2023 that will close this issue
@adp-atea adp-atea moved this from In Progress to Review in Portalo plėtra Aug 1, 2023
@sirex sirex moved this from Review to Todo in Portalo plėtra Nov 13, 2023
@adp-atea adp-atea moved this from Todo to In Progress in Portalo plėtra Nov 21, 2023
@adp-atea adp-atea moved this from In Progress to Review in Portalo plėtra Dec 13, 2023
@sirex sirex moved this from Review to Deploy in Portalo plėtra Jan 22, 2024
@github-project-automation github-project-automation bot moved this from Deploy to Done in Portalo plėtra Jan 24, 2024
@adp-atea adp-atea moved this from Done to Deploy in Portalo plėtra Jan 24, 2024
@sirex sirex moved this from Deploy to Test in Portalo plėtra Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Test
Development

Successfully merging a pull request may close this issue.

2 participants