Github user viirya commented on the issue:
https://github.com/apache/spark/pull/17371
Unfortunately, yes, allowing resolved attributes in user API will have this
kind of trouble.
> However, I don't think that piecemeal switching to unresolved attributes
is a good idea.
Agreed. Should we create new attributes after `withWatermark` to avoid the
problem? It might be cumbersome from the user side, however.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
