Details
-
Improvement
-
Status: Open
-
P3
-
Resolution: Unresolved
-
None
-
None
-
io-java-amqp, io-java-avro, io-java-aws, io-java-azure, io-java-cassandra, io-java-clickhouse, io-java-elasticsearch, io-java-files, io-java-gcp, io-java-hadoop-file-system, io-java-hadoop-format, io-java-hbase, io-java-hcatalog, io-java-jdbc, io-java-jms, io-java-kafka, io-java-kinesis, io-java-kudu, io-java-mongodb, io-java-mqtt, io-java-parquet, io-java-rabbitmq, io-java-redis, io-java-solr, io-java-text, io-java-tfrecord, io-java-tika, io-java-utilities, io-java-xml, sdk-java-core, sdk-java-harness
Description
A few modules used to have no rawtype errors. Now many of them do. Rawtypes are a legacy compatibility feature that should not be used in new code. Concretely, they obscure types (readability), mask errors (casts failing at runtime), and harm static analysis (checker framework recommends eliminating rawtypes as your first step)
Attachments
Issue Links
- is a clone of
-
BEAM-10402 [Umbrella] Eliminate nullability errors from Beam Java
- Open
- links to
1.
|
:sdks:java:extensions:hadoop-file-system uses legacy rawtypes | Open | Unassigned | |
2.
|
:sdks:java:io:azure uses legacy rawtypes | Open | Unassigned |