mgaido91 commented on code in PR #527:
URL: https://github.com/apache/livy/pull/527#discussion_r3379871793
##########
docs/programmatic-api.md:
##########
@@ -35,7 +35,7 @@ Add the Livy client dependency to your application's POM:
<dependency>
<groupId>org.apache.livy</groupId>
<artifactId>livy-client-http</artifactId>
- <version>0.7.0-incubating</version>
+ <version>0.7.0</version>
Review Comment:
that would not work, we either need to put the new version or keep the old
one.
##########
docs/rest-api.md:
##########
@@ -163,7 +163,7 @@ Creates a new interactive Scala, Python, or R shell in the
cluster.
</tr>
</table>
-<a id="footnote1">1</a>: Starting with version 0.5.0-incubating this field is
not required. To be
+<a id="footnote1">1</a>: Starting with version 0.5.0 this field is not
required. To be
Review Comment:
this should not be changed imho
##########
api/pom.xml:
##########
@@ -20,12 +20,12 @@
<parent>
<groupId>org.apache.livy</groupId>
<artifactId>livy-main</artifactId>
- <version>0.10.0-incubating-SNAPSHOT</version>
+ <version>0.10.0-SNAPSHOT</version>
Review Comment:
shall we move to 1.0 as we move out from incubating?
##########
docs/rest-api.md:
##########
@@ -773,7 +773,7 @@ A session represents an interactive shell.
</tr>
</table>
-Starting with version 0.5.0-incubating, each session can support all four
Scala, Python and R
+Starting with version 0.5.0, each session can support all four Scala, Python
and R
Review Comment:
ditto
##########
docs/rest-api.md:
##########
@@ -790,7 +790,7 @@ need to specify code kind (spark, pyspark, sparkr or sql)
during statement submi
To change the Python executable the session uses, Livy reads the path from
environment variable
``PYSPARK_PYTHON`` (Same as pyspark).
-Starting with version 0.5.0-incubating, session kind "pyspark3" is removed,
instead users require
+Starting with version 0.5.0, session kind "pyspark3" is removed, instead users
require
Review Comment:
ditto
--
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]
