bugraoz93 commented on PR #46849: URL: https://github.com/apache/airflow/pull/46849#issuecomment-2671936857
> Paging @bugraoz93! For `dags report`, was there a plan for getting the parsing duration time once that command is moved to be remote? I don't recall that being persisted anywhere. > > The "easy" answer is to just parse everything still with DagBag, you can follow the lead of `dags reserialize`. But, that kicks ^^ to down the road. Thanks for tagging Jed! We will support and get all the fields of `ParseImportError` (id, timestamp, filename, bundle_name and stacktrace). Yeah, you are right. I think parsing duration isn't part of it and does not persist in import errors. I believe we need to first include this on the `ParseImportError` object and all CRUD operations on the object such as in `airflow/dag_processing/collection.py` for Insert. Let's assume that won't be there when we first move it to remote. If needed, we may include this after 3.0, maybe around 3.1? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
