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.

Sign up for GitHub

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

Jump to bottom

[COST-4440] Warn when a partition already exists for OCP processing #4838

Merged
merged 3 commits into from
Dec 19, 2023
Merged

[COST-4440] Warn when a partition already exists for OCP processing #4838

merged 3 commits into from
Dec 19, 2023

Commits on Dec 19, 2023

  1. Warn when a partition already exists for OCP processing 

    This appears to be a problem only with OCP processing and only when two workers
are running the same workload practiaclly at the same exact time. This may
indicate a problem with our worker caching not preventing simultaneous
execution, or a problem with celery allowing duplicate tasks to run. We don’t
have enough information to determine that currently.

Since this is isolated to OCP processing, I fixed it only in the OPC processing
instead of making changes to update_summary_tables, which would affect all
provider types.
    @samdoran
    samdoran committed Dec 19, 2023
    Configuration menu
    Copy the full SHA
    2911e6c View commit details
    Browse the repository at this point in the history

  2. Add tests

    @samdoran
    samdoran committed Dec 19, 2023
    Configuration menu
    Copy the full SHA
    80dc915 View commit details
    Browse the repository at this point in the history

  3. Do not assume a TrinoQueryError was the cause of TrinoStatementExecError 

    We can Exception before raising TrinoStatementExecError, so it may not have the
expected attributes.
    @samdoran
    samdoran committed Dec 19, 2023
    Configuration menu
    Copy the full SHA
    91850f7 View commit details
    Browse the repository at this point in the history