You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GpuFileFormatWriter has code derived from Spark's FileFormatWriter, and SPARK-30227 added code to ensure the data writer is unconditionally closed when the write completes (either successfully or due to an error). GpuFileFormatWriter should do the same.
I don't believe our GPU writers rely on the close() method being invoked to free resources, but it would be good to fix this for both consistency with the Spark code and to cover the case where someone adds cleanup logic to a data writer close() method in the future.
The text was updated successfully, but these errors were encountered:
Make this more consistent with implementation of FileFormatWriter change implemented in SPARK-30227 by adding finallyBlock with close() call on dataWriter
Signed-off-by: Navin Kumar <navink@nvidia.com>
Make this more consistent with implementation of FileFormatWriter change implemented in SPARK-30227 by adding finallyBlock with close() call on dataWriter
Signed-off-by: Navin Kumar <navink@nvidia.com>
GpuFileFormatWriter has code derived from Spark's FileFormatWriter, and SPARK-30227 added code to ensure the data writer is unconditionally closed when the write completes (either successfully or due to an error). GpuFileFormatWriter should do the same.
I don't believe our GPU writers rely on the
close()
method being invoked to free resources, but it would be good to fix this for both consistency with the Spark code and to cover the case where someone adds cleanup logic to a data writerclose()
method in the future.The text was updated successfully, but these errors were encountered: