Github user maryannxue commented on the issue:

    https://github.com/apache/spark/pull/21187
  
    Thank you, @Tagar, for you comment! I think by saying "making FOR section 
optional", you actually mean to support "IN ANY".
    As you said and as I have pointed in my PR description, Oracle's "IN ANY" 
is only supported on XML. Besides, this version of Pivot SQL support is 
targeted to enable the front end that can leverage the existing runtime Pivot 
support, in which the values in "IN" clause are only allowed to be literals.
    That said, there's a few improvements we can make in the backend/runtime 
Pivot support. Some of them are easy, like "IN" value aliases; others are less 
so, like supporting "IN ANY". To be able to allow unspecified values, we might 
need to run another query at an early stage of this query's compilation, to get 
a list of all possible values, similar to what's been done in 
`RelationalGroupedDataset#pivot(String)`


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to