You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/10/09 17:10:03 UTC

[jira] [Commented] (BEAM-10556) Eliminate rawtype errors from Beam Java

    [ https://issues.apache.org/jira/browse/BEAM-10556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211207#comment-17211207 ] 

Beam JIRA Bot commented on BEAM-10556:
--------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.

> 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: starter
>          Time Spent: 3.5h
>  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.3.4#803005)