srowen commented on a change in pull request #27216: [SPARK-28588][DOC] 
Document SELECT statement in SQL Reference (Main page)
URL: https://github.com/apache/spark/pull/27216#discussion_r367518150
 
 

 ##########
 File path: docs/sql-ref-syntax-qry-select-window.md
 ##########
 @@ -0,0 +1,22 @@
+---
+layout: global
+title: WINDOW Clause
+displayTitle: WINDOW Clause
+license: |
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+ 
+     http://www.apache.org/licenses/LICENSE-2.0
+ 
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+---
+
+**This page is under construction**
 
 Review comment:
   Yeah I know, I'm not sure that was great as not all are filled out. Unless 
it would be hard to link them everywhere later, I wonder why they need to be 
here now? I don't see a difference w.r.t merging. I don't feel strongly but 
think we are just going to end up with more dummy pages that nobody fills out

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