-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Ingestion Pipeline to store run status #11857
Comments
include log link |
9 tasks
pmbrull
added a commit
that referenced
this issue
Dec 22, 2023
* Register StackTraceError in spec * Register StackTraceError in spec * Register StackTraceError in spec * Add todos * Update status * docs * format * Fix tests * Fix tests * Fix tests * Ignore generated * Fix tests * Fix tests * Tests * Try constants * Try constants * Print * Print * Print * order * Fix service name * fix ui error --------- Co-authored-by: Chirag Madlani <12962843+chirag-madlani@users.noreply.github.com>
chirag-madlani
added a commit
that referenced
this issue
Jan 24, 2024
9 tasks
chirag-madlani
added a commit
that referenced
this issue
Jan 24, 2024
chirag-madlani
added a commit
that referenced
this issue
Jan 24, 2024
chirag-madlani
added a commit
that referenced
this issue
Jan 25, 2024
chirag-madlani
added a commit
that referenced
this issue
Jan 25, 2024
chirag-madlani
added a commit
that referenced
this issue
Jan 25, 2024
Sachin-chaurasiya
added a commit
that referenced
this issue
Jan 25, 2024
#14841) * feat(ui): supported: #11857 show detailed run status for ingestion pipelines * fix user page issue and unit test for ingestion run status * Refactor IngestionRecentRun.test.tsx to use spread operator for executionRuns * fix unit test --------- Co-authored-by: Sachin Chaurasiya <sachinchaurasiyachotey87@gmail.com>
Sachin-chaurasiya
moved this from Ingestion - Bugs & Minor Features
to Done
in Release 1.3.0
Jan 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, ingestion pipelines have a pipelineStatus field which stores general run timings and state.
On top of this, we should publish the assets being processed at source/processor/sink, etc.
The text was updated successfully, but these errors were encountered: