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

chore(deps): update dependency bigquery-schema-generator to v1.6.1 #10

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 24, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
bigquery-schema-generator ==1.5 -> ==1.6.1 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

bxparks/bigquery-schema-generator (bigquery-schema-generator)

v1.6.1: 1.6.1 - fix amnesia during multipe type mismatches

Compare Source

  • 1.6.1 (2024-01-12)
    • Bug Fix: Prevent amnesia that causes multiple type mismatches warnings
      • If a data set contains multiple records with a column which do not
        match each other, then the old code would remove the corresponding
        internal schema_entry for that column, and print a warning message.
      • This means that subsequent records would recreate the schema_entry,
        and a subsequent mismatch would print another warning message.
      • This also meant that if there was a second record after the most
        recent mismatch, the script would output a schema entry for the
        mismatching column, corresponding to the type of the last record which
        was not marked as a mismatch.
      • The fix is to use a tombstone entry for the offending column, instead
        of deleting the schema_entry completely. Only a single warning
        message is printed, and the column is ignored for all subsequent
        records in the input data set.
      • See
        [Issue#98][https://github.com/bxparks/bigquery-schema-generator/issues/98](https://redirect.github.com/bxparks/bigquery-schema-generator/issues/98)8]
        which identified this problem which seems to have existed from the
        very beginning.

v1.5.1: 1.5.1 - add examples; update documentation

Compare Source

  • 1.5.1 (2022-12-04)
    • Add examples/*.py to demonstrate how to use SchemaGenerator as a
      library.
    • Update README.md to state that bq load --autodetect uses the first
      500 records. Previously, it scanned only the 100 records.
    • This is a maintenance release with no new features or bug fixes.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/bigquery-schema-generator-1.x branch from ef720bc to 2247c51 Compare January 13, 2024 09:08
@renovate renovate bot changed the title chore(deps): update dependency bigquery-schema-generator to v1.5.1 chore(deps): update dependency bigquery-schema-generator to v1.6.1 Jan 13, 2024
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

Successfully merging this pull request may close these issues.

0 participants