msawyer-palantir opened a new issue, #13733:
URL: https://github.com/apache/iceberg/issues/13733

   ### Apache Iceberg version
   
   1.9.2 (latest release)
   
   ### Query engine
   
   Spark
   
   ### Please describe the bug 🐞
   
   The main issue is that `VendedAdlsCredentialProvider` tries to call 
`Mono#block` even if in an async context, causing:
   ```
   Caused by: java.lang.IllegalStateException: block()/blockFirst()/blockLast() 
are blocking, which is not supported in thread parallel-1
        at 
reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:83)
        at reactor.core.publisher.Mono.block(Mono.java:1742)
        at 
org.apache.iceberg.azure.adlsv2.VendedAdlsCredentialProvider.credentialForAccount(VendedAdlsCredentialProvider.java:78)
        at 
org.apache.iceberg.azure.adlsv2.VendedAzureSasCredentialPolicy.maybeUpdateCredential(VendedAzureSasCredentialPolicy.java:58)
        at 
org.apache.iceberg.azure.adlsv2.VendedAzureSasCredentialPolicy.process(VendedAzureSasCredentialPolicy.java:46)
        at 
com.azure.core.http.HttpPipelineNextPolicy.process(HttpPipelineNextPolicy.java:81)
        at 
com.azure.storage.common.policy.MetadataValidationPolicy.process(MetadataValidationPolicy.java:45)
        at 
com.azure.core.http.HttpPipelineNextPolicy.process(HttpPipelineNextPolicy.java:81)
        at 
com.azure.core.http.policy.AddDatePolicy.lambda$process$0(AddDatePolicy.java:43)
        at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:45)
        ... 12 more
   ```
   
   But there are also other concurrency issues around that code which often 
lead to e.g. CMEs, e.g. the use of `HashMap#computeIfAbsent` by multiple 
threads at once.
   
   ### Willingness to contribute
   
   - [x] I can contribute a fix for this bug independently
   - [ ] I would be willing to contribute a fix for this bug with guidance from 
the Iceberg community
   - [ ] I cannot contribute a fix for this bug at this time


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to