subject:"\[GitHub\] \[spark\] JoshRosen commented on issue #26076\: \[SPARK\-29419\]\[SQL\] Fix Encoder thread\-safety bug in createDataset\(Seq\)"

[GitHub] [spark] JoshRosen commented on issue #26076: [SPARK-29419][SQL] Fix Encoder thread-safety bug in createDataset(Seq)

2020-01-18 Thread GitBox

JoshRosen commented on issue #26076: [SPARK-29419][SQL] Fix Encoder thread-safety bug in createDataset(Seq) URL: https://github.com/apache/spark/pull/26076#issuecomment-575970963 Hi @dongjoon-hyun, I spent some time prototyping a refactoring of `ExpressionEncoder` which separates

[GitHub] [spark] JoshRosen commented on issue #26076: [SPARK-29419][SQL] Fix Encoder thread-safety bug in createDataset(Seq)

2019-10-10 Thread GitBox

JoshRosen commented on issue #26076: [SPARK-29419][SQL] Fix Encoder thread-safety bug in createDataset(Seq) URL: https://github.com/apache/spark/pull/26076#issuecomment-540824919 > That sounds like a good idea to me. Can we do that first? I'll prototype this. If I get it working

[GitHub] [spark] JoshRosen commented on issue #26076: [SPARK-29419][SQL] Fix Encoder thread-safety bug in createDataset(Seq)

2019-10-09 Thread GitBox

JoshRosen commented on issue #26076: [SPARK-29419][SQL] Fix Encoder thread-safety bug in createDataset(Seq) URL: https://github.com/apache/spark/pull/26076#issuecomment-540211354 > But if we would like to fix all these problems, all public APIs accepting `Encoder` will need the copy.