Hi Denis,
Currently there’s no way to do SQL streaming besides ODBC/JDBC - that is,
there’s no other public API for it. I believe this is the first case when
we’re looking at a command that is supported only via drivers and not Java
API, so it’s an interesting question. Also streaming is no DDL, i
Alexander Paschenko created IGNITE-8204:
---
Summary: Tests hang with lazy query flag on
Key: IGNITE-8204
URL: https://issues.apache.org/jira/browse/IGNITE-8204
Project: Ignite
Issue Type
Alexander Paschenko created IGNITE-8050:
---
Summary: Throw a meaningful exception when user issues TX SQL
keyword with MVCC turned off
Key: IGNITE-8050
URL: https://issues.apache.org/jira/browse/IGNITE-8050
Alexander Paschenko created IGNITE-8016:
---
Summary: Make sure checks in QueryUtils.typeForQueryEntity are sane
Key: IGNITE-8016
URL: https://issues.apache.org/jira/browse/IGNITE-8016
Project
Alexander Paschenko created IGNITE-7956:
---
Summary: MVCC TX: cache eviction operations for key-value API
Key: IGNITE-7956
URL: https://issues.apache.org/jira/browse/IGNITE-7956
Project: Ignite
Alexander Paschenko created IGNITE-7955:
---
Summary: MVCC TX: cache peek for key-value API
Key: IGNITE-7955
URL: https://issues.apache.org/jira/browse/IGNITE-7955
Project: Ignite
Issue
Alexander Paschenko created IGNITE-7954:
---
Summary: MVCC TX: cache load routines for key-value API
Key: IGNITE-7954
URL: https://issues.apache.org/jira/browse/IGNITE-7954
Project: Ignite
Alexander Paschenko created IGNITE-7953:
---
Summary: MVCC TX: continuous queries
Key: IGNITE-7953
URL: https://issues.apache.org/jira/browse/IGNITE-7953
Project: Ignite
Issue Type: Task
Alexander Paschenko created IGNITE-7952:
---
Summary: MVCC TX: cache clear routines for key-value API
Key: IGNITE-7952
URL: https://issues.apache.org/jira/browse/IGNITE-7952
Project: Ignite
Alexander Paschenko created IGNITE-7942:
---
Summary: Document streaming in thin JDBC driver
Key: IGNITE-7942
URL: https://issues.apache.org/jira/browse/IGNITE-7942
Project: Ignite
Issue
Alexander Paschenko created IGNITE-7859:
---
Summary: SQL streaming support via native API
Key: IGNITE-7859
URL: https://issues.apache.org/jira/browse/IGNITE-7859
Project: Ignite
Issue
collected. This way
> pressure is moved to the client what increases cluster stability. Will that
> work?
>
> On Wed, Jan 24, 2018 at 6:23 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
>> Hello Igniters,
>>
>> I'd like to bring up
Alexander Paschenko created IGNITE-7738:
---
Summary: Allow 'multiple statements' in thin JDBC streaming mode
Key: IGNITE-7738
URL: https://issues.apache.org/jira/browse/IGNITE-7738
Proje
Alexander Paschenko created IGNITE-7664:
---
Summary: SQL: throw sane exception on unsupported SQL statements
Key: IGNITE-7664
URL: https://issues.apache.org/jira/browse/IGNITE-7664
Project: Ignite
Guys,
Right, first option is the way to go. Options 2 and 3 are surrogates
that do not free you from concept of cache but rather allow you to
obtain one.
I believe in near future we'll propose public API for cacheless queries.
- Alex
2018-02-01 19:38 GMT+03:00 Valentin Kulichenko :
> Nikolay,
>
Hello Igniters,
I'd like to bring up the discussion about implementation details of
https://issues.apache.org/jira/browse/IGNITE-6937 about
support of SELECT FOR UPDATE statements as a part of overall activity
on transactional SQL.
That kind of statements allows the user proactively obtain row le
Alexander Paschenko created IGNITE-7300:
---
Summary: Allow expressions in SQL INSERTs within transactions
Key: IGNITE-7300
URL: https://issues.apache.org/jira/browse/IGNITE-7300
Project: Ignite
Alexander Paschenko created IGNITE-7001:
---
Summary: Refactor dynamic indexes test to use SQL API
Key: IGNITE-7001
URL: https://issues.apache.org/jira/browse/IGNITE-7001
Project: Ignite
Alexander Paschenko created IGNITE-6996:
---
Summary: Smarter handling of id fields in SQL values
Key: IGNITE-6996
URL: https://issues.apache.org/jira/browse/IGNITE-6996
Project: Ignite
Alexander Paschenko created IGNITE-6950:
---
Summary: Update documentation for user facing CREATE TABLE params
Key: IGNITE-6950
URL: https://issues.apache.org/jira/browse/IGNITE-6950
Project
Alexander Paschenko created IGNITE-6637:
---
Summary: No proper cleanup of statements cache is done on table
drop
Key: IGNITE-6637
URL: https://issues.apache.org/jira/browse/IGNITE-6637
Project
Alexander Paschenko created IGNITE-6529:
---
Summary: JDBC drivers don't provide correct metadata about
columns' nullability
Key: IGNITE-6529
URL: https://issues.apache.org/jira/browse/I
Alexander Paschenko created IGNITE-6518:
---
Summary: Smarter analysis of INSERT and MERGE statements at
parsing stage
Key: IGNITE-6518
URL: https://issues.apache.org/jira/browse/IGNITE-6518
Alexander Paschenko created IGNITE-6270:
---
Summary: Rename user facing CREATE TABLE param names to split
words properly
Key: IGNITE-6270
URL: https://issues.apache.org/jira/browse/IGNITE-6270
Alexander Paschenko created IGNITE-6269:
---
Summary: Document CREATE TABLE param for cache write sync mode on
readme.io
Key: IGNITE-6269
URL: https://issues.apache.org/jira/browse/IGNITE-6269
Sounds good to me.
– Alex
2017-09-02 9:12 GMT+02:00 Denis Magda :
> Igniters,
>
> Consider a table and cache created this way:
>
> CREATE TABLE `city` (
> `ID` INT(11),
> `Name` CHAR(35),
> `CountryCode` CHAR(3),
> `District` CHAR(20),
> `Population` INT(11),
> PRIMARY KEY (`ID`, `Cou
parser and SQL engine
>> > step by step, little by little
>> > and one day drop H2 at all.
>> >
>> > Having own parser and engine will give us a freedom to any optimizations
>> > and any syntax we like.
>> >
>> > Also that wi
I'd like to point out that we already do have Ignite mode in H2 parser
(thanks Sergi) and thus have AFFINITY keyword support. Is is suggested
that we should abandon H2 way at all? Or should we suggest adding to
H2 only rather minor stuff (like some keywords for existing commands)
whilst introducing
Alexander Paschenko created IGNITE-5837:
---
Summary: Fix logic in DynamicIndexAbstractConcurrentSelfTest
Key: IGNITE-5837
URL: https://issues.apache.org/jira/browse/IGNITE-5837
Project: Ignite
Alexander Paschenko created IGNITE-5744:
---
Summary: Ignore non user caches when automatically choosing a
queryable cache inside JDBC driver
Key: IGNITE-5744
URL: https://issues.apache.org/jira/browse/IGNITE
Alexander Paschenko created IGNITE-5703:
---
Summary: Add CREATE TABLE param for cache write sync mode
Key: IGNITE-5703
URL: https://issues.apache.org/jira/browse/IGNITE-5703
Project: Ignite
Alexander Paschenko created IGNITE-5702:
---
Summary: Investigate H2DynamicIndexingComplexTest.testOperations
failures on replicated caches
Key: IGNITE-5702
URL: https://issues.apache.org/jira/browse/IGNITE
Alexander Paschenko created IGNITE-5654:
---
Summary: Distributed queries throw exception if joins with
replicated caches are not the last on the list
Key: IGNITE-5654
URL: https://issues.apache.org/jira
Alexander Paschenko created IGNITE-5653:
---
Summary: Add to query execution plan debug data for joins
Key: IGNITE-5653
URL: https://issues.apache.org/jira/browse/IGNITE-5653
Project: Ignite
Alexander Paschenko created IGNITE-5652:
---
Summary: Print slow query warnings on client node
Key: IGNITE-5652
URL: https://issues.apache.org/jira/browse/IGNITE-5652
Project: Ignite
Alexander Paschenko created IGNITE-5651:
---
Summary: Add long query timeout property
Key: IGNITE-5651
URL: https://issues.apache.org/jira/browse/IGNITE-5651
Project: Ignite
Issue Type
Alexander Paschenko created IGNITE-5650:
---
Summary: Add convenient API for getting column values
Key: IGNITE-5650
URL: https://issues.apache.org/jira/browse/IGNITE-5650
Project: Ignite
Alexander Paschenko created IGNITE-5482:
---
Summary: Implement basic caching of query results
Key: IGNITE-5482
URL: https://issues.apache.org/jira/browse/IGNITE-5482
Project: Ignite
Alexander Paschenko created IGNITE-5449:
---
Summary: Add complex DDL+DML test.
Key: IGNITE-5449
URL: https://issues.apache.org/jira/browse/IGNITE-5449
Project: Ignite
Issue Type: Task
IGNITE-5327 Create predefined cache templates for CREATE TABLE command
- minor comments left, ETA is Friday.
IGNITE-5380 Validate cache QueryEntities in discovery thread - in
progress, the meat of code is written, but need to add lots of tests.
ETA is Friday.
IGNITE-5188 Support AFFINITY KEY keyw
Hi guys,
To my knowledge, our binary format is currently resilient to
adding/removing fields of individual objects while having those
objects logically belonging to the same value type - thanks to all
efforts with binary resolvers and stable field sorting. Thus, ALTER
TABLE implemented as suggeste
Alexander Paschenko created IGNITE-5291:
---
Summary: SQL: plans cache does not clear on cache stop
Key: IGNITE-5291
URL: https://issues.apache.org/jira/browse/IGNITE-5291
Project: Ignite
Alexander Paschenko created IGNITE-5289:
---
Summary: SQL: forbid WITH queries
Key: IGNITE-5289
URL: https://issues.apache.org/jira/browse/IGNITE-5289
Project: Ignite
Issue Type: Task
Alexander Paschenko created IGNITE-5197:
---
Summary: Introduce AFFINITY KEY keywords and Ignite SQL mode to H2
Key: IGNITE-5197
URL: https://issues.apache.org/jira/browse/IGNITE-5197
Project
Alexander Paschenko created IGNITE-5116:
---
Summary: Handle cache destroy in DmlStatementsProcessor
Key: IGNITE-5116
URL: https://issues.apache.org/jira/browse/IGNITE-5116
Project: Ignite
Alexander Paschenko created IGNITE-4998:
---
Summary: Add more dynamic indexing tests for various cache modes
Key: IGNITE-4998
URL: https://issues.apache.org/jira/browse/IGNITE-4998
Project: Ignite
Alexander Paschenko created IGNITE-4953:
---
Summary: Rework logic of concurrent schema changes
Key: IGNITE-4953
URL: https://issues.apache.org/jira/browse/IGNITE-4953
Project: Ignite
> So basically in inherited class you are going co copy/paste base class
> methods and tweak them? I don't like this approach.
>
> Sergi
>
> 2017-04-12 14:07 GMT+03:00 Alexander Paschenko <
> alexander.a.pasche...@gmail.com>:
>
>> Sergi,
>>
>> As
i Vladykin написал:
> I don't see how you make H2 Parser extendable, you will have to add plugin
> call to every *potentially* extendable place in it. In general this does
> not work. As H2 guy I would also reject patch like this.
>
> Sergi
>
> 2017-04-12
see no reason to invent
> > > something different and confuse the users.
> > >
> > > [1]
> > > https://docs.microsoft.com/en-us/sql/t-sql/statements/create
> > > -table-transact-sql#syntax-1
> > > [2] https://www.postgresql.org/docs/9.1/static/sq
> Can you please provide an example of what the CREATE TABLE command would
> look like if we use WITH syntax from H2 vs. what you are proposing?
>
> D.
>
> On Tue, Apr 11, 2017 at 6:35 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
>> Hello Ig
Hello Igniters,
Yup, it's THAT time once again as we haven't ultimately settled on
anything with the subj. as of yet, but I believe that now with DDL on
its way this talk can't be avoided anymore (sorry guys).
The last time we talked about Ignite specific stuff we need to have in
CREATE TABLE (ke
Alexander Paschenko created IGNITE-4947:
---
Summary: Create AI 2.0 TC suites
Key: IGNITE-4947
URL: https://issues.apache.org/jira/browse/IGNITE-4947
Project: Ignite
Issue Type: Task
I've fixed https://issues.apache.org/jira/browse/IGNITE-4354, PR is
https://github.com/apache/ignite/pull/1759.
Pavel, thank you very much for bringing that to my attention.
- Alex
2017-04-07 20:28 GMT+03:00 Sergi Vladykin :
> A bunch of SQL related tickets is delayed until H2 release on the next
Alexander Paschenko created IGNITE-4905:
---
Summary: ClassCastException in DML benchmarks
Key: IGNITE-4905
URL: https://issues.apache.org/jira/browse/IGNITE-4905
Project: Ignite
Issue
Alexander Paschenko created IGNITE-4903:
---
Summary: More SQL side tests for CREATE/DROP INDEX
Key: IGNITE-4903
URL: https://issues.apache.org/jira/browse/IGNITE-4903
Project: Ignite
Hi Vyacheslav,
1: Yes, exactly.
2: Hash code is written for all BinaryObjects. Starting with Ignite
1.9, hashCode implementations of original classes are never used to
compute hash codes for corresponding binary objects.
- Alex
2017-03-23 12:58 GMT+03:00 Vyacheslav Daradur :
> Following second
I've written new sections about streaming both on that hidden jdbc 1.9
page and in (hidden for now and created by myself) DML 1.9 page -
figured that it might be a good thing to give the user a hint about
having a way to stream data via SQL on DML page as they could probably
miss it if we don't men
Alexander Paschenko created IGNITE-4742:
---
Summary: Flaky
IgniteCacheUpdateSqlQuerySelfTest.testTypeConversions
Key: IGNITE-4742
URL: https://issues.apache.org/jira/browse/IGNITE-4742
Project
Alexander Paschenko created IGNITE-4732:
---
Summary: Invalid ids quoting logic in DML and GridSqlFunction
Key: IGNITE-4732
URL: https://issues.apache.org/jira/browse/IGNITE-4732
Project: Ignite
ve distributed SQL support. Sergi Vladykin
> IGNITE-3013 Support sorted merge index for SQL Sergi Vladykin
> IGNITE-4212 Ignite Benchmarking Simplification and Automation Oleg Ostanin
> IGNITE-4169 Data streamer mode for DML Alexander Paschenko
> IGNITE-3710 Upgrade ignite-spark module to S
Folks,
Regarding INSERT semantics in JDBC DML streaming mode - I've left only
INSERTs supports as we'd agreed before.
However, current architecture of streaming related internals does not
give any clear way to intercept key duplicates and inform the user -
say, I can't just throw an exception fro
ev example with streamer - the Key { id1 = 5, id2
= 0 } that would be constructed from such query is just one key and is
handled by streamer as such while semantically that query is not about
ONE key but about ALL keys where id1 = 5.
- Alex
2017-02-10 11:49 GMT+03:00 Alexander Paschenko
:
> Dima
gt; > Are you suggesting that currently to execute a simple INSERT for 1 row we
>> > invoke a data streamer on Ignite API? How about an update by a primary
>> key?
>> > Why not execute a simple cache put in either case?
>> >
>> > I think we had
only be turned on if a certain flag on a JDBC connection is set, no?
>
> D.
>
> On Wed, Feb 8, 2017 at 7:00 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
> > Hello Igniters,
> >
> > I'd like to raise few questions regarding
Also, currently it's possible to run SELECTs on "streamed"
connections, and probably this is odd and should not be released too,
what do you think?
- Alex
2017-02-08 18:00 GMT+03:00 Alexander Paschenko
:
> Hello Igniters,
>
> I'd like to raise few questions reg
Hello Igniters,
I'd like to raise few questions regarding data streaming via DML statements.
Currently, all types of DML statements are supported (INSERT, UPDATE,
DELETE, MERGE).
UPDATE and DELETE are supported in streaming mode only when their
WHERE condition is bounded with _key and/or _val co
Alexander Paschenko created IGNITE-4660:
---
Summary: Add DML capabilities to legacy JDBC driver
Key: IGNITE-4660
URL: https://issues.apache.org/jira/browse/IGNITE-4660
Project: Ignite
andom syntax changes that are otherwise irrelevant to RDBMS and will
not be used by or implemented in H2 itself anyway.
- Alex
2017-01-30 4:18 GMT+03:00 Dmitriy Setrakyan :
> On Fri, Jan 27, 2017 at 8:51 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
>>
Guys,
And what would you say if I suggested that we implement custom grammar
support with ANTLR? It allows you to describe pretty much any grammar
in a declarative way, generates lexer and parser and then allows to
easily process parsed commands by implementing few (generated)
interfaces. Yesterda
Alexander Paschenko created IGNITE-4575:
---
Summary: Implement in Ignite wrapper for enums based on H2 user
value type
Key: IGNITE-4575
URL: https://issues.apache.org/jira/browse/IGNITE-4575
Alexander Paschenko created IGNITE-4574:
---
Summary: Introduce user value types to H2 w/custom conversion logic
Key: IGNITE-4574
URL: https://issues.apache.org/jira/browse/IGNITE-4574
Project
Alexander Paschenko created IGNITE-4573:
---
Summary: Optimize H2 comparisons w/constant
Key: IGNITE-4573
URL: https://issues.apache.org/jira/browse/IGNITE-4573
Project: Ignite
Issue Type
Alexander Paschenko created IGNITE-4570:
---
Summary: Handle CREATE INDEX statements
Key: IGNITE-4570
URL: https://issues.apache.org/jira/browse/IGNITE-4570
Project: Ignite
Issue Type
Alexander Paschenko created IGNITE-4569:
---
Summary: Create local portion of index w/table locking
Key: IGNITE-4569
URL: https://issues.apache.org/jira/browse/IGNITE-4569
Project: Ignite
Alexander Paschenko created IGNITE-4568:
---
Summary: Dynamically create distributed index
Key: IGNITE-4568
URL: https://issues.apache.org/jira/browse/IGNITE-4568
Project: Ignite
Issue
Alexander Paschenko created IGNITE-4567:
---
Summary: Design and implement means for distributed DDL statements
Key: IGNITE-4567
URL: https://issues.apache.org/jira/browse/IGNITE-4567
Project
Alexander Paschenko created IGNITE-4566:
---
Summary: Introduce IgniteCacheEx.createQueryIndex
Key: IGNITE-4566
URL: https://issues.apache.org/jira/browse/IGNITE-4566
Project: Ignite
Alexander Paschenko created IGNITE-4565:
---
Summary: Support CREATE INDEX DDL statements
Key: IGNITE-4565
URL: https://issues.apache.org/jira/browse/IGNITE-4565
Project: Ignite
Issue
Alexander Paschenko created IGNITE-4553:
---
Summary: Parse CREATE INDEX statements
Key: IGNITE-4553
URL: https://issues.apache.org/jira/browse/IGNITE-4553
Project: Ignite
Issue Type
Sergi,
Regarding CREATE SCHEMA/TABLE parsing:
2017-01-12 18:51 GMT+03:00 Sergi Vladykin :
> Hi,
>
> 1. For now I'm against inventing any custom SQL syntax and implementing
> parsing.
> Currently H2 supports the following syntax:
>
> CREATE TABLE test(...) WITH "myCustomParamString"
>
> This is en
Dima,
2017-01-13 21:20 GMT+03:00 Dmitriy Setrakyan :
> How about dynamic caches? Isn't the metadata already maintained across all
> nodes every time a new cache is created? What am I missing here?
Right, however, this section of the docs
https://apacheignite.readme.io/docs/jcache#section-dynamic
Vova,
2017-01-13 4:56 GMT+08:00 Vladimir Ozerov :
> I am not quite sure I understand the idea of "SCHEMA == cache". Consider
> some small database with, say, ~30 tables. And user wants to migrate to
> Ignite. How is he supposed to do so? 30 schemas leading to rewrite of all
> his SQL scripts? Or 3
his:
>> >
>> > CREATE SCHEMA "MyCacheName" WITH
>> > "cacheMode=REPLICATED;atomicityMode=ATOMIC"
>> >
>> > Sergi
>> >
>> > 2017-01-12 20:21 GMT+03:00 Alexander Paschenko <
>> > alexander.a.pasche...@
ation that could invoke custom parsing when
needed.
Not that we need it now - just in case.
- Alex
2017-01-13 2:16 GMT+08:00 Alexander Paschenko :
> Sergi,
>
> OK, great. Still, what's up with CREATE TABLE? After a bit of code
> digging, I currently don't see major obstacles
de=ATOMIC"
>
> Sergi
>
> 2017-01-12 20:21 GMT+03:00 Alexander Paschenko <
> alexander.a.pasche...@gmail.com>:
>
>> Sergi, Alexey G.,
>>
>> I see your point and am rather inclined to agree that we should let
>> current notion of "single sc
> key
>> > > > > > column somehow. Any cache property can be specified at the very
>> end
>> > > of
>> > > > > > table definition. Key columns can be determined as the ones with
>> > > > PRIMARY
>> > > > &
Hello Igniters,
I would like to start discussion about implementation of SQL DDL commands.
At the first stage, the most important ones seem to be CREATE TABLE
(that will obviously correspond to creation of a cache) and CREATE
INDEX.
Regarding first one: SQL command for CREATE TABLE does not cont
Alexander Paschenko created IGNITE-4490:
---
Summary: Optimize DML for fast INSERT and MERGE
Key: IGNITE-4490
URL: https://issues.apache.org/jira/browse/IGNITE-4490
Project: Ignite
Issue
Alexander Paschenko created IGNITE-4489:
---
Summary: Maintain correct MERGE semantic in DML
Key: IGNITE-4489
URL: https://issues.apache.org/jira/browse/IGNITE-4489
Project: Ignite
Issue
with
performance of bare cache operations reducing SQL related overhead to
nearly none at all. Hence I thought it was important to describe this
feature. Please review it and include into main doc as your heart
desires.
- Alex
2016-12-23 14:42 GMT+03:00 Alexander Paschenko
:
> Denis,
cs/dml
>> [2] http://apacheignite.gridgain.org/docs/sql-grid
>> [3] http://apacheignite.gridgain.org/docs/binary-
>> marshaller#handling-hash-code-generation-and-equals-execution
>>
>> —
>> Denis
>>
>> On Dec 9, 2016, at 12:34 AM, Alexander Paschenko <
Alexander Paschenko created IGNITE-4486:
---
Summary: Add serialVersionUID to AttributeNodeFilter
Key: IGNITE-4486
URL: https://issues.apache.org/jira/browse/IGNITE-4486
Project: Ignite
OK, will remove redundant query tasks creation for the case of DML
statements - they at least incur some GC overhead even if not context
switching.
- Alex
2016-12-20 12:49 GMT+03:00 Dmitriy Setrakyan :
> On Tue, Dec 20, 2016 at 1:23 AM, Alexander Paschenko <
> alexander.a.pasche...@
Any other thoughts?
>
> —
> Denis
>
> > On Dec 19, 2016, at 8:02 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
> >
> > OK folks, both data streamer support and batching support have been
> implemented.
> >
> >
ame logic.
> >
> > But anyway, +1 to removing nodeId property. It doesn't make much sense
> with
> > the new implementation of JDBC.
> >
> > -Val
> >
> > On Mon, Dec 19, 2016 at 10:15 AM, Alexander Paschenko <
> > alexander.a.pa
g to Denis, "even single (non batched) updates
> > or queries are sent as callables", which should be fixed in my view.
> >
> > D.
> >
> > On Mon, Dec 19, 2016 at 3:32 AM, Alexander Paschenko <
> > alexander.a.pasche...@gmail.com> wrote:
> >
&g
a/browse/IGNITE-4169
Regards,
Alex
2016-12-10 23:39 GMT+03:00 Dmitriy Setrakyan :
> Alex,
>
> It seams to me that replace semantic can be implemented with
> StreamReceiver, no?
>
> D.
>
> On Sat, Dec 10, 2016 at 2:54 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.
Dima, Val,
Introduction of updates has not changed public API at all (only
configuration, in some cases), so they work in this respect exactly
like SELECTs - by default they run on client node started by the
driver itself, but can be sent via the same callables mechanism to any
remote node by its
Sorry, "no relation w/JDBC" in my previous message should read "no relation
w/JDBC batching".
— Alex
10 дек. 2016 г. 1:52 PM пользователь "Alexander Paschenko" <
alexander.a.pasche...@gmail.com> написал:
> Dima,
>
> I would like to point ou
1 - 100 of 170 matches
Mail list logo
