-
Notifications
You must be signed in to change notification settings - Fork 6.7k
feat(pubsublite): attributes field in sink example #7405
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
Conversation
| # |-- key: binary (nullable = false) | ||
| # |-- data: binary (nullable = true) | ||
| # |-- event_timestamp: timestamp (nullable = true) | ||
| # |-- attributes: map (nullable = false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
our guide and everywhere actually specifies attributes is nullable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but our code doesn't really check since they are compatible ie our codebase is ok with nullable, I think it's fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jiangmichaellll Yes, all the fields can be nulls. It's just we are printing out of the dataframe created by the code above.
a3b327a to
6974675
Compare
6974675 to
32a24fb
Compare
Because this bug was fixed in the Pub/Sub Lite Spark connector googleapis/java-pubsublite-spark#261 with a new release, we are now able to write to Pub/Sub Lite with an
attributesfield.Updating the sample to show how to do that.