HeartSaVioR commented on PR #42940:
URL: https://github.com/apache/spark/pull/42940#issuecomment-1728653787
https://lists.apache.org/thread/ljronxf6bymvqjmlwpzy84gzgvnqrmoh
^^^ DISCUSSION thread in dev@.
--
This is an automated message from the Apache Git Service.
To respond to the
HeartSaVioR commented on PR #42940:
URL: https://github.com/apache/spark/pull/42940#issuecomment-1726773266
Thanks, merging to master.
(I'll probably raise a discussion to dev@ for porting back to 3.5/3.4.)
--
This is an automated message from the Apache Git Service.
To respond to the
HeartSaVioR commented on PR #42940:
URL: https://github.com/apache/spark/pull/42940#issuecomment-1726769354
https://github.com/HeartSaVioR/spark/runs/16947355981
Looks like the test is flaky rather than consistent failure, it passed
before rebasing and also passed locally.
HeartSaVioR commented on PR #42940:
URL: https://github.com/apache/spark/pull/42940#issuecomment-1726601027
Ah I commented too late :) Thanks for your support!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
HeartSaVioR commented on PR #42940:
URL: https://github.com/apache/spark/pull/42940#issuecomment-1726600452
> As we are already in the status that sources not supporting
Trigger.AvailableNow can work with the wrapper instead of simply failing since
Trigger.Once is deprecated, it sounds
HeartSaVioR commented on PR #42940:
URL: https://github.com/apache/spark/pull/42940#issuecomment-1726572679
Looks like python side env issue. I'll rebase and see the chance to be
already fixed in latest master.
--
This is an automated message from the Apache Git Service.
To respond to
HeartSaVioR commented on PR #42940:
URL: https://github.com/apache/spark/pull/42940#issuecomment-1720694800
cc. @zsxwing @brkyvz @viirya @anishshri-db Mind taking a look? Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
