You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@solr.apache.org by ja...@apache.org on 2022/04/08 13:24:03 UTC

[solr] branch branch_9x updated (bb4119c041d -> 4f4f359b8e3)

This is an automated email from the ASF dual-hosted git repository.

janhoy pushed a change to branch branch_9x
in repository https://gitbox.apache.org/repos/asf/solr.git


    from bb4119c041d SOLR-16143: Fix integration test cleanup & snapshot failure cases (#789)
     new 2faec39a966 Update ref-guide system requirements page (#795)
     new 4f4f359b8e3 SOLR-15761 Remove jdbc() stream from refGuide since it can no longer be used as an expression (#788)

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../pages/system-requirements.adoc                 | 67 ++++++++------------
 .../query-guide/pages/stream-source-reference.adoc | 74 ----------------------
 2 files changed, 25 insertions(+), 116 deletions(-)


[solr] 01/02: Update ref-guide system requirements page (#795)

Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

janhoy pushed a commit to branch branch_9x
in repository https://gitbox.apache.org/repos/asf/solr.git

commit 2faec39a9668c30810481536bc0bfab6ce03050e
Author: Jan Høydahl <ja...@users.noreply.github.com>
AuthorDate: Fri Apr 8 15:00:37 2022 +0200

    Update ref-guide system requirements page (#795)
    
    (cherry picked from commit bea30b959f927ee306c0b35909eed4b64817f9a2)
---
 .../pages/system-requirements.adoc                 | 67 ++++++++--------------
 1 file changed, 25 insertions(+), 42 deletions(-)

diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/system-requirements.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/system-requirements.adoc
index f0c494e571b..a3f2e827be6 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/system-requirements.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/system-requirements.adoc
@@ -27,20 +27,19 @@ Solr is tested on several versions of Linux, macOS and Windows.
 //TODO: this with the next big section on Java fragments the Java requirements too much. Consider merging sections.
 === Java Requirements
 
-You will need the Java Runtime Environment (JRE) version 1.8 or higher.
+You will need the Java Runtime Environment (JRE) version 11 or higher.
 At a command line, check your Java version like this:
 
 [source,bash]
 ----
 $ java -version
-java version "1.8.0_60"
-Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
-Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
+openjdk version "11.0.14.1" 2022-02-08
+OpenJDK Runtime Environment Temurin-11.0.14.1+1 (build 11.0.14.1+1)
+OpenJDK 64-Bit Server VM Temurin-11.0.14.1+1 (build 11.0.14.1+1, mixed mode)
 ----
 
 The exact output will vary, but you need to make sure you meet the minimum version requirement.
 We also recommend choosing a version that is not end-of-life from its vendor.
-Oracle/OpenJDK are the most tested JREs and are preferred.
 It's also preferred to use the latest available official release.
 
 Some versions of Java VM have bugs that may impact your implementation.
@@ -49,64 +48,48 @@ To be sure, check the page https://cwiki.apache.org/confluence/display/LUCENE/Ja
 === Sources for Java
 
 Java is available from a number of providers.
-Lucene and Solr regularly test with https://jdk.java.net/[OpenJDK] and Oracle versions of Java.
-Some are free, others have a cost, some provide security patches and support, others do not.
+The official Docker image for Solr uses the Temurin distribution of OpenJDK from the https://adoptium.net/[Adoptium project].
+Solr regularly test with https://adoptium.net/temurin/releases[Temurin], https://jdk.java.net/[OpenJDK] and Oracle versions of Java.
+Some distributions are free, others have a cost, some provide security patches and support, others do not.
 We recommend you read the article https://medium.com/@javachampions/java-is-still-free-2-0-0-6b9aa8d6d244[Java is still free by Java Champions] to help you decide.
 
-The Lucene project does not endorse any particular provider of Java.
+The Solr project does not endorse any particular provider of Java.
 
 NOTE: While we reference the Java Development (JDK) on this page, any Java Runtime Environment (JRE) associated with the referenced JDKs is acceptable.
 
-== Java and Lucene/Solr Combinations
+== Java and Solr Combinations
 
-Each Lucene/Solr release has an extensively tested minimum Java version.
-For instance the minimum Java version for Solr 8 is Java 8.
-This section provides guidance when running Lucene/Solr with a more recent Java version than the minimum specified.
+Each Solr release has an extensively tested minimum Java version.
+For instance the minimum Java version for Solr 9 is Java 11.
+This section provides guidance when running Solr with a more recent Java version than the minimum specified.
 
 * OpenJDK and Oracle Java distributions are tested extensively and will continue to be tested going forward.
 ** Distributions of Java from other sources are not regularly tested by our testing infrastructure, therefore you must test Java from those sources in your environment.
-** For the purposes of Lucene and Solr, Oracle's Java and OpenJDK are identical.
+** For the purposes of Solr, Oracle's Java and OpenJDK are identical.
 * Upgrading Java is not required with the understanding that no Java bugs will be addressed unless you are using a version of Java that provides LTS.
-* Java 8 has been extensively tested by both automated tests and users through Solr 8.
-Long Term Support (LTS) for Java 8 is provided by some sources, see https://medium.com/@javachampions/java-is-still-free-2-0-0-6b9aa8d6d244[Java is still free].
+* Java 11 has been extensively tested by both automated tests and users through Solr 9.
+Long Term Support (LTS) for Java 11 is provided from several sources.
 * The project's testing infrastructure continuously tests with the minimum and greater versions of Java for each development branch.
-* Java 9 and 10 have no LTS.
-For this reason, Java 11 is preferred over 9 or 10 when upgrading Java.
+* Java 12, 13, 14, 15 and 16 have no LTS.
+For this reason, Java 17 is preferred when upgrading Java.
 * For specific questions the http://solr.apache.org/community.html#mailing-lists-chat[Solr User's List] is a great resource.
 
 === Project Testing of Java-Solr Combinations
 Solr and Lucene run a continuous integration model, running automated unit and integration tests using several versions of Java.
 In addition, some organizations also maintain their own test infrastructure and feed their results back to the community.
 
-Our continuous testing is against the two code lines under active development, Solr 8x and the future Solr 9.0:
+Our continuous testing is against the two code lines under active development, Solr 9x and the future Solr 10.0:
 
-* Lucene/Solr 8.x is the current stable release line and will have "point releases", i.e., 8.1, 8.2, etc., until Lucene/Solr 9.0 is released.
-** Solr 8.x is currently tested against Java 8, 9, 10, 11, 12 and (pre-release) 13.
-* There is also development and testing with the future Lucene/Solr 9.x release line, which will require Java 11 as a minimum version.
-This line is currently tested against Java 11, 12 and (pre-release) 13.
-* Lucene/Solr 7.x and earlier release lines are not tested on a continuous basis.
+* Solr 9.x is the current stable release line and will have "point releases", i.e., 9.1, 9.2, etc., until Solr 10.0 is released.
+** Solr 9.x is currently tested against Java 11, 17 and 18-prerelease.
+* There is also development and testing with the future Solr 10.x release line.
+* /Solr 8.x and earlier release lines are not tested on a continuous basis.
 
-=== Released Lucene/Solr and Java Versions
+=== Released Solr and Java Versions
 The success rate in our automated tests is similar with all the Java versions tested with the following caveats.
 
-==== Lucene/Solr Prior to 7.0
-
-* Lucene/Solr 7.0 was the first version that successfully passed our tests using Java 9 and higher.
-You should avoid Java 9 or later for Lucene/Solr 6.x or earlier.
-
-==== Lucene/Solr 7.x
-
-* Requires Java 8 or higher.
-* This version had continuous testing with Java 9, 10, 11, 12 and the pre-release version of Java 13.
-Regular testing stopped when Lucene/Solr 8.0 was released.
-* Hadoop with Java 9+ may not work in all situations, test in your environment.
-* Kerberos with Java 9+ may not work in all situations, test in your environment.
-* Be sure to test with SSL/TLS and/or authorization enabled in your environment if you require either when using Java 9+.
-
-==== Lucene/Solr 8.x
+==== Solr 8.x
 
 * Requires Java 8 or higher.
-* This version has continuous testing with Java 9, 10, 11, 12 and the pre-release version of Java 13.
+* This version did have continuous testing with Java 9, 10, 11, 12 and the pre-release version of Java 13.
 * There were known issues with Kerberos with Java 9+ prior to Solr 8.1.
-If using 8.0, you should test in your environment.
-* Be sure to test with SSL/TLS and/or authorization enabled in your environment if you require either when using Java 9+.


[solr] 02/02: SOLR-15761 Remove jdbc() stream from refGuide since it can no longer be used as an expression (#788)

Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

janhoy pushed a commit to branch branch_9x
in repository https://gitbox.apache.org/repos/asf/solr.git

commit 4f4f359b8e37576b7fb9a87cc4ce0bad3e0c8140
Author: Jan Høydahl <ja...@users.noreply.github.com>
AuthorDate: Fri Apr 8 15:02:09 2022 +0200

    SOLR-15761 Remove jdbc() stream from refGuide since it can no longer be used as an expression (#788)
    
    (cherry picked from commit 5a5989e5b6164091243dd29cfe327b5eaac2cfbd)
---
 .../query-guide/pages/stream-source-reference.adoc | 74 ----------------------
 1 file changed, 74 deletions(-)

diff --git a/solr/solr-ref-guide/modules/query-guide/pages/stream-source-reference.adoc b/solr/solr-ref-guide/modules/query-guide/pages/stream-source-reference.adoc
index abe3b97e5d8..bb58b3a056a 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/stream-source-reference.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/stream-source-reference.adoc
@@ -57,80 +57,6 @@ expr=search(collection1,
        sort="a_f asc, a_i asc")
 ----
 
-== jdbc
-
-The `jdbc` function searches a JDBC datasource and emits a stream of tuples representing the JDBC result set.
-Each row in the result set is translated into a tuple and each tuple contains all the cell values for that row.
-
-=== jdbc Parameters
-
-* `connection`: (Mandatory) JDBC formatted connection string to whatever driver you are using.
-* `sql`: (Mandatory) query to pass off to the JDBC endpoint
-* `sort`: (Mandatory) The sort criteria indicating how the data coming out of the JDBC stream is sorted
-* `driver`: The name of the JDBC driver used for the connection.
-If provided then the driver class will attempt to be loaded into the JVM.
-If not provided then it is assumed that the driver is already loaded into the JVM.
-Some drivers require explicit loading so this option is provided.
-* `[driverProperty]`: One or more properties to pass to the JDBC driver during connection.
-The format is `propertyName="propertyValue"`.
-You can provide as many of these properties as you'd like and they will all be passed to the connection.
-
-=== Connections and Drivers
-
-Because some JDBC drivers require explicit loading the `driver` parameter can be used to provide the driver class name.
-If provided, then during stream construction the driver will be loaded.
-If the driver cannot be loaded because the class is not found on the classpath, then stream construction will fail.
-
-When the JDBC stream is opened it will validate that a driver can be found for the provided connection string.
-If a driver cannot be found (because it hasn't been loaded) then the open will fail.
-
-=== Datatypes
-
-Due to the inherent differences in datatypes across JDBC sources the following datatypes are supported.
-The table indicates what Java type will be used for a given JDBC type.
-Types marked as requiring conversion will go through a conversion for each value of that type.
-For performance reasons the cell data types are only considered when the stream is opened as this is when the converters are created.
-
-[width="100%",options="header",]
-|===
-|JDBC Type |Java Type |Requires Conversion
-|String |String |No
-|Short |Long |Yes
-|Integer |Long |Yes
-|Long |Long |No
-|Float |Double |Yes
-|Double |Double |No
-|Boolean |Boolean |No
-|===
-
-=== jdbc Syntax
-
-A basic `jdbc` expression:
-
-[source,text]
-----
-jdbc(
-    connection="jdbc:hsqldb:mem:.",
-    sql="select NAME, ADDRESS, EMAIL, AGE from PEOPLE where AGE > 25 order by AGE, NAME DESC",
-    sort="AGE asc, NAME desc",
-    driver="org.hsqldb.jdbcDriver"
-)
-----
-
-A `jdbc` expression that passes a property to the driver:
-
-[source,text]
-----
-// get_column_name is a property to pass to the hsqldb driver
-jdbc(
-    connection="jdbc:hsqldb:mem:.",
-    sql="select NAME as FIRST_NAME, ADDRESS, EMAIL, AGE from PEOPLE where AGE > 25 order by AGE, NAME DESC",
-    sort="AGE asc, NAME desc",
-    driver="org.hsqldb.jdbcDriver",
-    get_column_name="false"
-)
-----
-
 == drill
 
 The `drill` function is designed to support efficient high cardinality aggregation.