feat: expose _TABLE_SUFFIX pseudocolumn for wildcard tables#1689
Closed
feat: expose _TABLE_SUFFIX pseudocolumn for wildcard tables#1689
_TABLE_SUFFIX pseudocolumn for wildcard tables#1689Conversation
…g pseudocolumns
Fixes this code sample:
import bigframes.pandas as bpd
df = bpd.read_gbq("bigquery-public-data.google_analytics_sample.ga_sessions_*")
df[df["_TABLE_SUFFIX"] == "20161204"].peek()
…ython-bigquery-dataframes into b405773140-wildcard
4 tasks
Collaborator
Author
|
Marking as |
Collaborator
Author
|
Closing for now. Will revisit this if / when we get to the pseudocolumns feature in our backlog. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1661 and #1691
Towards internal issues b/405773140 and b/416285785 🦕