[jira] [Updated] (KAFKA-14490) Consider using UncheckdIOException instead of IOException in the log layer

["Ismael Juma (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-14490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismael Juma updated KAFKA-14490:
--------------------------------
    Description: 
IOException is a checked exception, which makes it difficult to use with lambdas. We should consider using UncheckdIOException instead.

I'll add notes below with code that could be simplified if we did this:

1. The private constructor of LazyIndex could take a factory method instead of all parameters and IndexType (like the Scala code used to). This would avoid some repetition and some unsafe casts.

  was:IOException is a checked exception, which makes it difficult to use with lambdas. We should consider using UncheckdIOException instead.


> Consider using UncheckdIOException instead of IOException in the log layer
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-14490
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14490
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Ismael Juma
>            Priority: Major
>
> IOException is a checked exception, which makes it difficult to use with lambdas. We should consider using UncheckdIOException instead.
> I'll add notes below with code that could be simplified if we did this:
> 1. The private constructor of LazyIndex could take a factory method instead of all parameters and IndexType (like the Scala code used to). This would avoid some repetition and some unsafe casts.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)