panbingkun commented on PR #43751:

   > I think it's more natural to follow the same behavior of the LIKE operator 
here. It seems all databases follow it (except for Hive before 4.0). Spark 
followed Hive at the beginning and that's probably why Spark has this special 
and weird behavior for the LIKE pattern in SHOW TABLES.
   > In fact, this is out of Spark's control, as it's the external catalog that 
applies the pattern string. We should follow the industry standard for defining 
the v2 catalog API. We should also update the SHOW TABLES doc page to mention 
the ideal behavior of the pattern string, as well as the legacy Hive behavior.
   Okay, let me handle it in this PR and update the document.
   Additionally, do we need to add `a legacy configuration` (default is `new` 
behavior) to determine whether it is using the `legacy` behavior or the `new` 
   (PS: Yes, from the first PR, we can see that the original author's intention 
was to respect the legacy hive behavior.
   <img width="903" alt="image" 

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:

For queries about this service, please contact Infrastructure at:

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to