You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/07/24 22:38:00 UTC

[jira] [Updated] (FLINK-27725) Create tests for TypeInformation and TypeSerializer classes in table

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

Flink Jira Bot updated FLINK-27725:
-----------------------------------
    Labels: pull-request-available stale-major  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Create tests for TypeInformation and TypeSerializer classes in table
> --------------------------------------------------------------------
>
>                 Key: FLINK-27725
>                 URL: https://issues.apache.org/jira/browse/FLINK-27725
>             Project: Flink
>          Issue Type: Technical Debt
>          Components: Table SQL / Runtime
>    Affects Versions: 1.16.0
>            Reporter: Alexander Preuss
>            Priority: Major
>              Labels: pull-request-available, stale-major
>
> During the implementation of FLINK-27527 we had to add `flink-table-planner` as a test dependency to `flink-tests`.
> This created test failures for the reflection tests checking test coverage for `TypeInformation` and `TypeSerializer` classes as shown here:
> [https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=35851&view=logs&j=56de72e1-1902-5ae5-06bd-77ee907eed59&t=237d25ca-be06-5918-2b0a-41d0694dace8&l=6738]
> To mitigate the issue and unblock FLINK-27527 we extended the whitelist as a temporary solution but there should be a better solution in place. Some of the classes are deprecated but others are not and should probably have tests created to improve the coverage.



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