maropu commented on issue #28224: [SPARK-31429][SQL][DOC] Automatically 
generates a SQL document for built-in functions
URL: https://github.com/apache/spark/pull/28224#issuecomment-614339948
 
 
   > Can we still have window functions here? In SQL Syntax section, I am 
focusing on SQL syntax, I don't have a list of window functions and their 
descriptions there.
   
   Yea, we can do. I'll update later. Thanks!
   
   
   > Can we list other function categories as well? such as Math functions, 
string functions, sorting functions, udf functions? 
   
   Yea, we can do, too. But, in this PR, I just want to focus on the python 
code and the basic set of built-in functions. As for the other function groups, 
I think we need to discuss more about which functions should be listed, or not.
   
   > Also, functions.scala puts Array functions in Collection functions group. 
Shall we use Collection functions instead of Array functions?
   
   Yea, I noticed that, but the collection group includes array, map, and JSON 
functions. I personally think splitting it into the three groups looks 
easy-to-serach for users. WDYT?
   
   > In the left side menu, can we have Built-in Functions and User Defined 
Functions, and put the three UDFs as subcategories?
   
   The original one had multiple document pages for the functions, so it had 
one more hierarchy. But, the script generates a single page for them. So, I 
think we don't need the hierarchy. If we need to improve the structure, feel 
free to do it as follow-up.
   
   
   
   
   
   
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to