snuyanzin opened a new pull request, #27269:
URL: https://github.com/apache/flink/pull/27269

   
   ## What is the purpose of the change
   
   This is seems to be another case for FLINK-20539 which was never covered by 
any test before.
   The way how it could be reproduced
   1.
   ```sql
   CREATE TABLE `testcat.db.tb1.v1` (
     `field0` ROW<`nested` STRING NOT NULL>
   ) WITH (
    'connector' = 'values',
    'bounded' = 'true'
   );
   ```
   2.
   ```sql
   CREATE TABLE `testcat.db.tb2.v1` (
     `field0` ROW< `nested0` ROW< `nested1` ROW<`nested2` ROW<`nested3` STRING 
NOT NULL>>>>
   ) WITH (
    'connector' = 'values',
    'bounded' = 'true'
   )
   ```
   3.
   ```sql
   SELECT 1
   FROM `testcat.db.tb2.v1` t2
   WHERE NOT EXISTS (
       SELECT 1
       FROM `testcat.db.tb1.v1` t
       WHERE `t`.`field0`.`nested` = `t2`.`field0`.`nested0`.`nested2`.`nested3`
   )
   ```
   ## Brief change log
   
   *(for example:)*
     - *The TaskInfo is stored in the blob store on job creation time as a 
persistent artifact*
     - *Deployments RPC transmits only the blob storage reference*
     - *TaskManagers retrieve the TaskInfo from the blob cache*
   
   
   ## Verifying this change
   Semantic test added
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): ( no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: ( no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): ( no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to