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

Show status of the document analysis #102

Open
flavioamieiro opened this issue Nov 6, 2013 · 3 comments
Open

Show status of the document analysis #102

flavioamieiro opened this issue Nov 6, 2013 · 3 comments
Milestone

Comments

@flavioamieiro
Copy link
Member

This involves being able to know the status of a pipeline, which we don't have access to right now.

My first idea was to have a field for that in the document and set it to the right status when the pipeline finishes, but for this the backend would need to be able to change data in the frontend.

Any ideas?

@turicas
Copy link
Contributor

turicas commented Nov 6, 2013

Maybe we can modify our store in backend to write meta-data information about what workers finished and the total of workers for that pipeline (as we have _properties we can have _workers, _finished_workers, _running_workers or something like this). With this feature we won't have notion of time, but we'll have more information about what is happening on the pipeline (but only if we really need this information).

Having this or not, I think the status of a document can be one of these:

  • Waiting for processing
  • Processing
  • Done
  • Error processing

@flavioamieiro
Copy link
Member Author

This does sound like a good idea, and the StoreProxy (in the frontend) can look at this metadata and show it better to the user.

We already know when there was an error ("_error" and "_exception" are created in the mongodb document). We just need to show the user which analysis the error affects.

@turicas
Copy link
Contributor

turicas commented Nov 6, 2013

I think to start we could have only status and show the contents of _exception if there is an error. Then the ability to re-run the pipeline for that document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants