[
https://issues.apache.org/jira/browse/BEAM-10556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-10556:
-----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the
pull request resolve the issue? If so, could you please mark it resolved? This
will help the project have a clear view of its open issues.
> Eliminate rawtype errors from Beam Java
> ---------------------------------------
>
> Key: BEAM-10556
> URL: https://issues.apache.org/jira/browse/BEAM-10556
> Project: Beam
> Issue Type: Improvement
> Components: 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
> Reporter: Kenneth Knowles
> Priority: P3
> Labels: Clarified, starter
> Time Spent: 6h 50m
> Remaining Estimate: 0h
>
> 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)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
