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
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:
>
>>
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
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
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
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
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
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
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
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
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 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
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
> 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
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
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
> 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
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
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
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
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
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
Hi Ignite Community!
My name is Alex. I want to contribute to Apache Ignite and am starting
with the following issue: IGNITE-3233. Any suggestions are welcome.
Thanks!
Alexey in Jira
https://issues.apache.org/jira/browse/IGNITE-3227?focusedCommentId=15360787
suggested that we remove int sized methods from CacheProxy, and he has
indeed removed them, but IgniteCache has such new methods too. Should
we let them be or maybe it would be better to get rid of them? Ple
Hell Igniters,
In this thread I would like to share and discuss some thoughts on DML
operations' implementation, so let's start and keep it here. Everyone
is of course welcome to share their suggestions.
For starters, I was thinking about semantics of INSERT. In traditional
RDBMSs, INSERT works o
> Thus, I suggest that we implement MERGE as a separate operation backed by
> putIfAbsent operation, while INSERT will be implemented via put.
Sorry, of course I meant that MERGE has to be put-based, while INSERT
has to be putIfAbsent-based.
2016-07-20 12:30 GMT+03:00 Alexander Pas
I agree. It looks like we first of all need some algorithm of key
generation for new objects, and it does not necessarily have to be
involved with DDL. The first suggestion that comes to my mind on that
matter is, obviously, marking some method of the class persisted with
magical annotation - so th
t/putIfAbsent operations but probably we
>> > > will need some batching like putAllIfAbsent for efficiency)?
>> > >
>> > > As for API, we still will need to have a single entry point for all SQL
>> > > queries/commands to allow any console work with it trans
y be we
>> need to change in some backward compatible way this Query hierarchy to get
>> rid of extra methods but the idea is still the same.
>>
>> Sergi
>>
>> 2016-07-26 14:34 GMT+03:00 Alexander Paschenko <
>> alexander.a.pasche...@gmail.com>:
>>
&
rn the same
>> information, so it will not be empty (beauty is restored!).
>>
>> Sergi
>>
>>
>>
>> 2016-07-26 18:24 GMT+03:00 Alexander Paschenko <
>> alexander.a.pasche...@gmail.com>:
>>
>> > I see your point. But what about my concern
cness, or in some other weird way). Is this what
we really want? Or am I missing something in your point?
- Alex
2016-07-27 12:51 GMT+03:00 Sergi Vladykin :
> Exactly. This will allow our Jdbc driver to work transparently.
>
> Sergi
>
> 2016-07-27 12:40 GMT+03:00
OK, I've found that bold cast to QueryCursor in IgniteCacheProxy
and had a look at how SqlFieldsQuery is used in JDBC driver. Thanks.
- Alex
2016-07-27 13:02 GMT+03:00 Sergi Vladykin :
> Where did you see R in SqlFieldsQuery?
>
> Sergi
>
> 2016-07-27 12:59 GMT+03:00
rably change
existing logic.
- Alex
2016-07-27 14:23 GMT+03:00 Sergi Vladykin :
> Please don't forget about ODBC, .NET and Visor. They all have to work in
> the same way.
>
> Sergi
>
> 2016-07-27 14:15 GMT+03:00 Alexander Paschenko <
> alexander.a.pasche...@gmail.c
gt; > Please don't forget about ODBC, .NET and Visor. They all have to work in
>> > the same way.
>> >
>> > Sergi
>> >
>> > 2016-07-27 14:15 GMT+03:00 Alexander Paschenko <
>> > alexander.a.pasche...@gmail.com>:
>>
Guys,
Here's documented version of current API changes - it's quite modest
https://goo.gl/Y6Cv1b
- Alex
2016-07-28 20:34 GMT+03:00 Alexander Paschenko
:
> Sergi,
>
> OK, I've done it as you said, thanks.
> Now working on binary marshaller support.
>
> - Alex
&g
Dmitriy,
Good point, however, currently there's no way to distinguish hash code
of zero which is a valid case from missing hash code. We probably
should enhance binary builder for it to handle this case.
- Alex
2016-08-02 9:47 GMT+03:00 Dmitriy Setrakyan :
> On Mon, Aug 1, 2016 at 11:38 PM, Vlad
How about we supply hash code evaluation routine via, say, JavaScript?
Yakov has already suggested that in the beginning of this thread.
- Alex
2016-08-02 10:46 GMT+03:00 Alexey Goncharuk :
> I still fail to understand the use case then. Do we want to support insert
> via SQL and get via regular
and origValueClass. These
> classes can be unavailable on nodes and most of the time we will have to
> work with binary format. Please make sure that this case is correctly
> handled.
>
> Sergi
>
> 2016-08-01 18:14 GMT+03:00 Alexander Paschenko <
> alexander.a.pasche...@gmail
me happy and put all your design into the ticket
> instead of sending it around in emails?
>
> On top of that, the link you provided is protected. I cannot access it.
>
> D.
>
> On Tue, Aug 2, 2016 at 8:24 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wr
able, what do you
think?
- Alex
2016-08-03 3:15 GMT+03:00 Dmitriy Setrakyan :
> On Tue, Aug 2, 2016 at 2:21 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
>> Dmitriy,
>>
>> Sorry, link access fixed, please check now.
>> Will sum up curre
as I see it from the code, always fails fast.
Which behavior do you think it would be better to implement in Ignite?
- Alex
2016-08-03 15:47 GMT+03:00 Alexander Paschenko
:
> Guys,
>
> I have few questions about current state of the art regarding JDBC driver.
>
> First: in JdbcPre
Sergi,
> Why do we need to count query arguments? Can anyone clarify?
Say, to make parameter index checks early like all major vendors do.
That's why they are counted now.
> Also about new public APIs. I don't see why we need SqlFieldsQuery.isQuery,
> looks like it has to be optional, so it will
first query execution. Lets just drop
> this argument counting.
>
> We should not show SqlFieldsQuery.isQuery on public API if it is useless
> for the end users. If this stuff is needed for Jdbc we have to find a way
> to make it private.
>
> Sergi
>
> 2016-08-
as to be a reference to a
>> predefined
>> >> object and the reference comparison (not equals) is used to check if the
>> >> field is initialized by the user.
>> >>
>> >> Refer to IgniteConfiguration.failureDetectionTimeout and
>> >>
Dmitriy,
I've updated the issue with current state of work and proposal for
data streamer use, please have a look/advise.
- Alex
2016-08-04 21:16 GMT+03:00 Alexander Paschenko
:
> Sergi,
>
> OK, all fixed, there's no trace of update operations in public API now,
> thanks.
e.
> >
> > Sergi
> >
> > 2016-08-06 6:18 GMT+03:00 Dmitriy Setrakyan :
> >
> > > How about we add a property - auto-generate hashCode() in binary
> > > configuration. If set, then we auto-generate the hashCode() every time
> a
> >
Hello Igniters,
As DML support is near, it's critical that we agree on how we generate
hash codes for new keys in presence of binary marshaller. Actually,
this discussion isn't new - please see its beginning here:
http://apache-ignite-developers.2346864.n4.nabble.com/All-BinaryObjects-created-by-
>> implementation should use the reflection coming over all the fields a key
>> has ignoring the ones that are marked with “transient” keyword. If a user
>> wants to control the default resolver's logic then he can label all the
>> fields that mustn’t be of a final has code
e documentation.
>
> —
> Denis
>
>> On Sep 28, 2016, at 9:33 AM, Alexander Paschenko
>> wrote:
>>
>> Dmitry, Denis,
>>
>> OK, but I think it's necessary to address also the cases when there's
>> no actual class for the key, and its f
me
> way that may be useful here.
>
> —
> Denis
>
>> On Sep 28, 2016, at 9:53 AM, Alexander Paschenko
>> wrote:
>>
>> Denis,
>>
>> That's not what I was asking about.
>> Currently DML implementation allows for dymanic instantiation of key
Also MERGE.
2016-09-29 2:10 GMT+03:00 Denis Magda :
> You need a hash code only for INSERT operation, right?
>
> —
> Denis
>
>> On Sep 28, 2016, at 3:47 PM, Alexander Paschenko
>> wrote:
>>
>> But what if the user works from some kind of console and just t
s. Here we’re trying to apply a workaround by listing key's fields in
>> > INSERT/MERGE and the task is to properly re-construct the key on our side
>> > using only specific fields.
>> >
>> > Is my understanding correct for all the bullets abov
nk here?
>>
>> Also, we must make sure that hashcode fields do not change. I believe you
>> should have validation in the code on startup of a system or of a cache,
>> and throw an exception if it fails.
>>
>> D.
>>
>> On Thu, Sep 29, 2016 at 9:08 AM,
I've posted proposed example of hash code resolver interface and XML
configuration for classless key on issue page
https://issues.apache.org/jira/browse/IGNITE-2294.
2016-09-29 20:16 GMT+03:00 Dmitriy Setrakyan :
> On Thu, Sep 29, 2016 at 9:57 AM, Denis Magda wrote:
>
>> Alex,
>>
>> A minor note
imply add 2 methods to the
>> > BinaryObjectHashCodeResolver: isUseEquals() and computeEquals(). Having
>> > said that, I am OK with current design, we can always add equals support
>> > later.
>> >
>> > Otherwise, looks good.
>> >
>> >
Current status on DML:
- Basic data streamer support implemented (basicness is mostly about
configuration - say, currently there's no way to specify streamer's
batch size via JDBC driver, but this can be improved easily).
- Fixed all minor stuff agreed with Vladimir.
- There are some tests that
L and ODBC (PDO) related changes into 1.8
>> >>> branch? I’m looking forward to go through PDO [1] documentation and be
>> sure
>> >>> that everything works as described on my side.
>> >>>
>> >>> *Pavel,*
>> >>>
>> >>> Do you think
1-22 11:29 GMT+03:00 Alexander Paschenko
:
> Vlad,
>
> Most likely today.
>
> - Alex
>
> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
>> Igniters,
>>
>> I went through remaining tickets assigned to 1.8 and it seems that we are
>> pretty close to release.
!
>>
>> Igniters,
>> Let's finalize all remaining tickets in the scope of *ignite-1.8 *branch.
>> Hopefully we will be ready for vote in several days.
>>
>> Vladimir.
>>
>> On Wed, Nov 23, 2016 at 11:01 AM, Alexander Paschenko <
>> alexand
,
>> > >
>> > > Awesome news, thanks for making this happen!
>> > >
>> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I
>> > start
>> > > testing that PHP-PDO guidance [1] is correct?
>> > >
>
DML is done as for now, example is done too, currently there's no open
issues related with it (besides documentation which I'm working on).
Yesterday's problem turned out to be binary/SQL engine (pre DML)
related and is currently in won't fix state as agreed with Vlad, I've
created issues detailing
lt;https://issues.apache.org/jira/browse/IGNITE-4331>
>
> How would it affect the overall user experience? Could you provide DML
> queries examples that won’t work due to the bug.
>
> —
> Denis
>
>> On Nov 29, 2016, at 9:14 AM, Alexander Paschenko
>> wrote:
>>
/jira/browse/IGNITE-2310 <
>> > >>>>> https://issues.apache.org/jira/browse/IGNITE-2310>
>> > >>>>>
>> > >>>>> Essentially, it allows locking a partition while a remote
>> computation
>> > >>
Hello Igniters,
One of the major improvements to DML has to be support of batch
statements. I'd like to discuss its implementation. The suggested
approach is to rewrite given query turning it from few INSERTs into
single statement and processing arguments accordingly. I suggest this
as long as the
pairs due to high overhead on concurrency and other
> bookkeeping. Instead, it is better to pre-batch key-value pairs before
> giving them to streamer.
>
> Vladimir.
>
> [1]
> https://docs.oracle.com/javase/8/docs/api/java/sql/PreparedStatement.html#addBatch--
>
> On T
h
>>
>> Also we need to keep in mind that data streamer has poor performance when
>> adding single key-value pairs due to high overhead on concurrency and other
>> bookkeeping. Instead, it is better to pre-batch key-value pairs before
>> giving them to streamer.
>>
&
l
> [2] https://apacheignite.readme.io/docs/distributed-dml-to-be-reviewe
> [3] https://apacheignite.readme.io/docs/dml#section-insert
>
> —
> Denis
>
> On Dec 8, 2016, at 1:35 AM, Alexander Paschenko
> wrote:
>
> Denis,
>
> it's all ready, JDBC driver page is also upd
t; > > > >
> > > > > > I see no reason to forbid Streamer usage from non-batched
> statement
> > > > > > execution.
> > > > > > It is common that users already have their ETL tools and you
> can't
> > be
> > > > > sure
> > >
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
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
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.
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
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
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.
> >
> >
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...@
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 <
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,
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
> 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
>> > > > &
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
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
his:
>> >
>> > CREATE SCHEMA "MyCacheName" WITH
>> > "cacheMode=REPLICATED;atomicityMode=ATOMIC"
>> >
>> > Sergi
>> >
>> > 2017-01-12 20:21 GMT+03:00 Alexander Paschenko <
>> > alexander.a.pasche...@
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
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
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
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
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
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,
>
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-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-4566:
---
Summary: Introduce IgniteCacheEx.createQueryIndex
Key: IGNITE-4566
URL: https://issues.apache.org/jira/browse/IGNITE-4566
Project: Ignite
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-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-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-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-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-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-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-4660:
---
Summary: Add DML capabilities to legacy JDBC driver
Key: IGNITE-4660
URL: https://issues.apache.org/jira/browse/IGNITE-4660
Project: Ignite
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
1 - 100 of 170 matches
Mail list logo
