You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/05/06 07:12:45 UTC

[GitHub] [flink] dawidwys opened a new pull request #8349: [FLINK-12411][table-planner][tests] Workaround limited support of not nullable fields in window aggregation

dawidwys opened a new pull request #8349: [FLINK-12411][table-planner][tests] Workaround limited support of not nullable fields in window aggregation
URL: https://github.com/apache/flink/pull/8349
 
 
   ## What is the purpose of the change
   
   This does not fix the problem. It just makes the e2e test pass. For a
   proper fix of the underlying problem see [FLINK-12249](https://issues.apache.org/jira/browse/FLINK-12249).
   
   
   ## Brief change log
   
     - Produce nullable type in `CASE ... WHEN` statement. The added `NULL` value will never be generated. It's sole purpose is to deceive the planner.
   
   
   ## Verifying this change
   
   It changes only `test_streaming_sql.sh`.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no /** don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services