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

Detect columns used in generated columns #256

Merged
merged 11 commits into from
Aug 30, 2024
Merged

Detect columns used in generated columns #256

merged 11 commits into from
Aug 30, 2024

Commits on Aug 29, 2024

  1. detect columns used in generated columns to make subscriptions work s… 

    …eamlessly
    @jeromegn
    jeromegn committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    93ed989 View commit details
    Browse the repository at this point in the history

  2. recursively go through each generated from columns in case they're al… 

    …so generated
    @jeromegn
    jeromegn committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    5aa8dc6 View commit details
    Browse the repository at this point in the history

  3. record a few more metrics to see how long processing changes in subsc… 

    …riptions is taking and how often we fallback to async send in channel
    @jeromegn
    jeromegn committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    7fab74a View commit details
    Browse the repository at this point in the history

  4. provide corro-query-hash header to better identify subscriptions in m… 

    …etrics and still keep metrics cardinality low
    @jeromegn
    jeromegn committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    e828252 View commit details
    Browse the repository at this point in the history

  5. warn log when very slow to process changes in subscription

    @jeromegn
    jeromegn committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    b107ecf View commit details
    Browse the repository at this point in the history

  6. lower threshold ot process changes buffer. use a sleep as a deadline … 

    …instead of an interval to process buffer
    @jeromegn
    jeromegn committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    2168f4a View commit details
    Browse the repository at this point in the history

  7. try 100 changes instead of 250, as the threshold

    @jeromegn
    jeromegn committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    53eafe9 View commit details
    Browse the repository at this point in the history

  8. go the other way, try 1000

    @jeromegn
    jeromegn committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    cffbeeb View commit details
    Browse the repository at this point in the history

  9. gather processing time per table

    @jeromegn
    jeromegn committed Aug 29, 2024
    Configuration menu
    Copy the full SHA
    000a6da View commit details
    Browse the repository at this point in the history

Commits on Aug 30, 2024

  1. add sql_hash field to a few log entries

    @jeromegn
    jeromegn committed Aug 30, 2024
    Configuration menu
    Copy the full SHA
    78018b9 View commit details
    Browse the repository at this point in the history

  2. reset the deadline whatever happens if we reach it

    @jeromegn
    jeromegn committed Aug 30, 2024
    Configuration menu
    Copy the full SHA
    eef541e View commit details
    Browse the repository at this point in the history