korlov42 commented on code in PR #858: URL: https://github.com/apache/ignite-3/pull/858#discussion_r892168734
########## docs/_docs/sql/java.adoc: ########## @@ -0,0 +1,81 @@ +// 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. += Java SQL API + +In your Java projects, you can use the Java SQL API to execute SQL statements and getting results. All operations are executed as a part of sql session. You can create a session with default parameters by using a `sql.createSession()` method, or use an `sql.sessionBuilder` to configure it for your environment. Sessions are usually long-lived objects that can be used in multiple threads and may hold data server-side. Session object is light-weight, and Ignite manages resources automatically in failover scenarios (for example, for disconnects). Keep in mind that you need to close the session manually by using the `close()` method when the session is no longer needed. Here is how you usually set up a session: + +[source, java] +---- +Session ses = sql.createSession(); +Session ses = sql.sessionBuilder().defaultSchema("PUBLIC").build(); +---- + +The `execute` method accepts a query String, or a Statement object, that can be created by using `sql.createStatement()` and `sql.statementBuilder()` methods. Stetements are light-weight objects and can be reused in multiple threads or sessions. Setting set by using `statementBuilder` override session settings for this statement. Here is how you usually set up a statement: + +[source, java] +---- +Statement stmt = sql.createStatement(sqlQueryString)); +Statement stmt = sql.statementBuilder().query(sqlQueryString)).build(); +---- + + +== Creating Tables + +Here is an example of how you can create a new table on a cluster: + +[source, java] +---- +try (ResultSet rs = ses.execute(null, + null, + `CREATE TABLE SYNCH(ID INT PRIMARY KEY, VAL0 INT)` +); Review Comment: ```suggestion try (ResultSet rs = ses.execute(null, "CREATE TABLE SYNCH(ID INT PRIMARY KEY, VAL0 INT)") ) { // no-op } ``` -- 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]
