mingmwang opened a new issue, #4366:
URL: https://github.com/apache/arrow-datafusion/issues/4366

   **Describe the bug**
   A clear and concise description of what the bug is.
   
   ````
           let ctx = create_join_context_with_null_ids("t1_id", "t2_id", 
repartition_joins).unwrap();
           let sql = "SELECT t1_id, t1_name FROM t1 WHERE NOT EXISTS (SELECT 1 
FROM t2 WHERE t1_id = t2_id and t1_id > 11) ORDER BY t1_id";
           let actual = execute_to_batches(&ctx, sql).await;
           let expected = vec![
               "+-------+---------+",
               "| t1_id | t1_name |",
               "+-------+---------+",
               "| 11    | a       |",
               "| 11    | a       |",
               "| 33    | c       |",
               "|       | e       |",
               "+-------+---------+",
           ];
           assert_batches_eq!(expected, &actual);
   
   ````
   
   
   called `Result::unwrap()` on an `Err` value: "SchemaError(FieldNotFound { 
field: Column { relation: Some(\"t1\"), name: \"t1_id\" }, valid_fields: 
Some([Column { relation: Some(\"t2\"), name: \"t2_id\" }]) }) at Creating 
physical plan for 'SELECT t1_id, t1_name FROM t1 WHERE NOT EXISTS (SELECT 1 
FROM t2 WHERE t1_id = t2_id and t1_id > 11) ORDER BY t1_id': Sort: t1.t1_id ASC 
NULLS LAST\n  Projection: t1.t1_id, t1.t1_name\n    LeftAnti Join: t1.t1_id = 
t2.t2_id\n      TableScan: t1 projection=[t1_id, t1_name]\n      Filter: 
CAST(t1.t1_id AS Int64) > Int64(11)\n        TableScan: t2 projection=[t2_id]"
   
   
   **To Reproduce**
   Steps to reproduce the behavior:
   
   **Expected behavior**
   A clear and concise description of what you expected to happen.
   
   **Additional context**
   Add any other context about the problem here.
   


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