Re: [PR] Prevent deadlock in Jackson [iceberg]

2024-05-27 Thread via GitHub
Fokko commented on PR #10379: URL: https://github.com/apache/iceberg/pull/10379#issuecomment-2133619097 @snazy Good point. I've added a point for the sync this Wednesday: https://docs.google.com/document/d/1YuGhUdukLP5gGiqCbk0A5_Wifqe2CZWgOd3TbhY3UQg/ -- This is an automated message from

Re: [PR] Prevent deadlock in Jackson [iceberg]

2024-05-27 Thread via GitHub
snazy commented on PR #10379: URL: https://github.com/apache/iceberg/pull/10379#issuecomment-2133611386 In Iceberg maybe - but that doesn't prevent other code to initialize the classes concurrently -- This is an automated message from the Apache Git Service. To respond to the message, ple

Re: [PR] Prevent deadlock in Jackson [iceberg]

2024-05-27 Thread via GitHub
Fokko commented on PR #10379: URL: https://github.com/apache/iceberg/pull/10379#issuecomment-2133609274 @snazy Thanks for working on this. Have you encountered a deadlock? It looks like we have some additional synchronization logic on the Iceberg side. -- This is an automated message from

Re: [PR] Prevent deadlock in Jackson [iceberg]

2024-05-27 Thread via GitHub
snazy commented on PR #10379: URL: https://github.com/apache/iceberg/pull/10379#issuecomment-2133603788 @Fokko thanks for merging. I suspect the deadlock is a big enough risk to include this change in 1.5.3? -- This is an automated message from the Apache Git Service. To respond to the me

Re: [PR] Prevent deadlock in Jackson [iceberg]

2024-05-27 Thread via GitHub
Fokko merged PR #10379: URL: https://github.com/apache/iceberg/pull/10379 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apa