Re: Re[2]: IGNITE-6499 Compact NULL fields

[steve.hostett...@gmail.com]

Ok gotcha, so it is not going to make it. 

Just to note that we are dragging this since before v2.0 and just a reminder
that someone else tried a similar thing before v2 and it got blocked because
it was too much of a change for v2.

Typically the type of things that we can never change because it is too much
of an impact.

BinaryObject format is not optimal far for it and if we cannot change it
incrementally nor in a big bang...



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-13244) Transaction commit completes successfully if partition is lost on commit phase

[Sergey Uttsel (Jira)]

Sergey Uttsel created IGNITE-13244:
--

 Summary: Transaction commit completes successfully if partition is 
lost on commit phase
 Key: IGNITE-13244
 URL: https://issues.apache.org/jira/browse/IGNITE-13244
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Uttsel
Assignee: Sergey Uttsel






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13243) Add tests for commands to manage metadata

[Taras Ledkov (Jira)]

Taras Ledkov created IGNITE-13243:
-

 Summary: Add tests for commands to manage metadata
 Key: IGNITE-13243
 URL: https://issues.apache.org/jira/browse/IGNITE-13243
 Project: Ignite
  Issue Type: Test
  Components: sql
Reporter: Taras Ledkov
Assignee: Taras Ledkov


Adds tests for commands to manage metadata (see GG-29247)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

[Ilya Kasnacheev]

Hello!

I have also set up nightly builds to (hopefully) build 2.9

Regards,
-- 
Ilya Kasnacheev


вт, 7 июл. 2020 г. в 17:04, Ilya Kasnacheev :

> Hello!
>
> I have changed the schedule condition so ignite-2.9 will be run instead.
> Please check if it works tomorrow.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 7 июл. 2020 г. в 16:42, Alex Plehanov :
>
>> Guys,
>>
>> Can somebody help with creating scheduled build triggers for nightly "Run
>> All" on TC for "ignite-2.9" branch?
>>
>> Also, I found that we still have a nightly "Run All" for "ignite-2.8"
>> branch [1]. Do we still need it? Or just forgot to remove it after
>> release?
>>
>> [1] :
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAllNightly_IgniteTests24Java8=ignite-2.8=buildTypeStatusDiv
>>
>> пт, 3 июл. 2020 г. в 23:18, Alex Plehanov :
>>
>> > Anton, thank you.
>> >
>> > Guys,
>> >
>> > I've cut the release branch. From now on please pin resolved in the
>> master
>> > branch tickets to 2.10 release in Jira and cherry-pick targeted to 2.9
>> > tickets to ignite-2.9 branch.
>> >
>> > As far as the release branch cut was delayed, I propose to move code
>> > freeze dates by one week (to 17 July 2020). WDYT?
>> >
>> > I've moved long-time inactive non-blocker tickets (except documentation
>> > related, we will deal with them later) from 2.9 release, please check
>> your
>> > Jira issues to have the correct "Fix version" field if your ticket is
>> > planned to 2.9 release.
>> >
>> > All currently pinned to 2.9 issues can be found on the release page [1].
>> >
>> > I didn't get about [2] ticket mentioned in this thread, are we going to
>> > include it into 2.9? Ivan Bessonov, Sergey Chugunov, can you please
>> clarify?
>> >
>> > [1]:
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>> > [2]: https://issues.apache.org/jira/browse/IGNITE-13156
>> >
>> > пн, 29 июн. 2020 г. в 12:38, Anton Vinogradov :
>> >
>> >> You're now at the "Ignite Release Managers" group.
>> >> Please check you gain access.
>> >>
>> >> On Fri, Jun 26, 2020 at 9:38 PM Alex Plehanov > >
>> >> wrote:
>> >>
>> >> > Guys,
>> >> >
>> >> > I've created the 2.9 release confluence page [1].
>> >> > Also, I found that I don't have permission to Team City release
>> tasks.
>> >> Can
>> >> > anyone give me such permissions?
>> >> >
>> >> > [1]:
>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.9
>> >> >
>> >> > пт, 26 июн. 2020 г. в 13:38, Alexey Zinoviev > >:
>> >> >
>> >> > > Igniters
>> >> > >
>> >> > > Unfortunately, the ML model export/import feature
>> >> > >  is under
>> >> development
>> >> > > yet.
>> >> > > I need to delay it before the 2.10 release.
>> >> > >
>> >> > >
>> >> > >
>> >> > > пт, 26 июн. 2020 г. в 06:50, Alex Plehanov <
>> plehanov.a...@gmail.com>:
>> >> > >
>> >> > > > Denis,
>> >> > > >
>> >> > > > Yes, I still ready to manage it.
>> >> > > > Today I will prepare a release page on wiki and will try to go
>> over
>> >> > > tickets
>> >> > > > list.
>> >> > > > Also, I have plans to cut the branch by the end of next week if
>> >> there
>> >> > are
>> >> > > > no objections.
>> >> > > >
>> >> > > >
>> >> > > > пт, 26 июн. 2020 г. в 03:48, Denis Magda :
>> >> > > >
>> >> > > > > Igniters,
>> >> > > > >
>> >> > > > > Are we moving forward with this release? Alex Plehanov, are you
>> >> still
>> >> > > > ready
>> >> > > > > to manage it? It seems like everyone agreed with the timeline
>> you
>> >> > > > proposed
>> >> > > > > in the very beginning.
>> >> > > > >
>> >> > > > > -
>> >> > > > > Denis
>> >> > > > >
>> >> > > > >
>> >> > > > > On Tue, Jun 16, 2020 at 8:52 AM Denis Magda > >
>> >> > wrote:
>> >> > > > >
>> >> > > > > > Sergey, Ivan,
>> >> > > > > >
>> >> > > > > > Could you please check the questions below? If it's
>> >> time-consuming
>> >> > to
>> >> > > > > > rework continuous queries, then the new mode can become
>> >> available
>> >> > in
>> >> > > > the
>> >> > > > > > experimental state and should not let register continuous
>> >> queries
>> >> > to
>> >> > > > > avoid
>> >> > > > > > potential deadlocks. Overall, this design gap in continuous
>> >> queries
>> >> > > was
>> >> > > > > > like a bomb that has just detonated [1]. Anyway, this new
>> >> > > connectivity
>> >> > > > > mode
>> >> > > > > > will be priceless even if you can't use continuous queries
>> with
>> >> > them
>> >> > > > > > because right now we cannot even start a thick client inside
>> of
>> >> a
>> >> > > > > > serverless function.
>> >> > > > > >
>> >> > > > > > Alexey Plehanov,
>> >> > > > > >
>> >> > > > > > It looks like we can proceed with the release taking your
>> >> > timelines.
>> >> > > > > >
>> >> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-13156
>> >> > > > > >
>> >> > > > > > -
>> >> > > > > > Denis
>> >> > > > > >
>> >> > > > > >
>> >> > > > > > On Wed, Jun 10, 2020 at 4:16 PM Denis Magda <
>> dma...@apache.org>
>> >> > 

Re: IEP-50 Thin Client Continuous Queries

[Pavel Tupitsyn]

Igor, Alex,

I was aware of the duplicates issue with the initial query, but I did not
give it a second thought.

Now I see that Vladimir was right - Initial query seems to be pointless,
since users can
achieve the same by simply invoking the regular query.

I will remove Initial Query from the IEP and POC next week if there are no
objections by then.


On Fri, Jul 10, 2020 at 3:58 PM Alex Plehanov 
wrote:

> Igor, Pavel,
>
> Here is discussion about removal: [1]
>
> [1] :
>
> http://apache-ignite-developers.2346864.n4.nabble.com/ContinuousQueryWithTransformer-implementation-questions-2-td21418i20.html#a22041
>
> пт, 10 июл. 2020 г. в 17:44, Igor Sapego :
>
> > Can not find proposal to remove them, so maybe it was not on devlist,
> > but here is discussion about the problem: [1]
> >
> > [1] -
> >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Continuous-queries-and-duplicates-td39444.html
> >
> > Best Regards,
> > Igor
> >
> >
> > On Fri, Jul 10, 2020 at 3:27 PM Pavel Tupitsyn 
> > wrote:
> >
> > > > What's about "stop" message? How can user unsubscribe from receiving
> > > notifications?
> > > OP_RESOURCE_CLOSE is used for that. I've updated the IEP in an attempt
> to
> > > make this cleaner.
> > >
> > > >  I've seen discussions on removing initial query from continuous
> > queries
> > > Interesting, I'm not aware of this. Can you please link those
> > discussions?
> > >
> > > On Fri, Jul 10, 2020 at 2:04 PM Igor Sapego 
> wrote:
> > >
> > > > Pavel,
> > > >
> > > > What's about "stop" message? How can user unsubscribe from receiving
> > > > notifications?
> > > >
> > > > Also, I believe I've seen discussions on removing initial query from
> > > > continuous queries,
> > > > as there are not any guarantees about getting consistent results with
> > > them.
> > > > Should
> > > > we avoid adding them in thin protocol maybe? It would also simplify
> > > > protocol a lot.
> > > >
> > > > Best Regards,
> > > > Igor
> > > >
> > > >
> > > > On Tue, Jun 30, 2020 at 2:39 PM Pavel Tupitsyn  >
> > > > wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > > Let's discuss Thin Client Continuous Queries,
> > > > > I've prepared an IEP [1] and a PoC [2].
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-50%3A+Thin+Client+Continuous+Queries
> > > > >
> > > > > [2] https://github.com/apache/ignite/pull/7966
> > > > >
> > > >
> > >
> >
>

Re: IEP-50 Thin Client Continuous Queries

[Alex Plehanov]

Igor, Pavel,

Here is discussion about removal: [1]

[1] :
http://apache-ignite-developers.2346864.n4.nabble.com/ContinuousQueryWithTransformer-implementation-questions-2-td21418i20.html#a22041

пт, 10 июл. 2020 г. в 17:44, Igor Sapego :

> Can not find proposal to remove them, so maybe it was not on devlist,
> but here is discussion about the problem: [1]
>
> [1] -
>
> http://apache-ignite-developers.2346864.n4.nabble.com/Continuous-queries-and-duplicates-td39444.html
>
> Best Regards,
> Igor
>
>
> On Fri, Jul 10, 2020 at 3:27 PM Pavel Tupitsyn 
> wrote:
>
> > > What's about "stop" message? How can user unsubscribe from receiving
> > notifications?
> > OP_RESOURCE_CLOSE is used for that. I've updated the IEP in an attempt to
> > make this cleaner.
> >
> > >  I've seen discussions on removing initial query from continuous
> queries
> > Interesting, I'm not aware of this. Can you please link those
> discussions?
> >
> > On Fri, Jul 10, 2020 at 2:04 PM Igor Sapego  wrote:
> >
> > > Pavel,
> > >
> > > What's about "stop" message? How can user unsubscribe from receiving
> > > notifications?
> > >
> > > Also, I believe I've seen discussions on removing initial query from
> > > continuous queries,
> > > as there are not any guarantees about getting consistent results with
> > them.
> > > Should
> > > we avoid adding them in thin protocol maybe? It would also simplify
> > > protocol a lot.
> > >
> > > Best Regards,
> > > Igor
> > >
> > >
> > > On Tue, Jun 30, 2020 at 2:39 PM Pavel Tupitsyn 
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > Let's discuss Thin Client Continuous Queries,
> > > > I've prepared an IEP [1] and a PoC [2].
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-50%3A+Thin+Client+Continuous+Queries
> > > >
> > > > [2] https://github.com/apache/ignite/pull/7966
> > > >
> > >
> >
>

Re: IEP-50 Thin Client Continuous Queries

[Igor Sapego]

Can not find proposal to remove them, so maybe it was not on devlist,
but here is discussion about the problem: [1]

[1] -
http://apache-ignite-developers.2346864.n4.nabble.com/Continuous-queries-and-duplicates-td39444.html

Best Regards,
Igor


On Fri, Jul 10, 2020 at 3:27 PM Pavel Tupitsyn  wrote:

> > What's about "stop" message? How can user unsubscribe from receiving
> notifications?
> OP_RESOURCE_CLOSE is used for that. I've updated the IEP in an attempt to
> make this cleaner.
>
> >  I've seen discussions on removing initial query from continuous queries
> Interesting, I'm not aware of this. Can you please link those discussions?
>
> On Fri, Jul 10, 2020 at 2:04 PM Igor Sapego  wrote:
>
> > Pavel,
> >
> > What's about "stop" message? How can user unsubscribe from receiving
> > notifications?
> >
> > Also, I believe I've seen discussions on removing initial query from
> > continuous queries,
> > as there are not any guarantees about getting consistent results with
> them.
> > Should
> > we avoid adding them in thin protocol maybe? It would also simplify
> > protocol a lot.
> >
> > Best Regards,
> > Igor
> >
> >
> > On Tue, Jun 30, 2020 at 2:39 PM Pavel Tupitsyn 
> > wrote:
> >
> > > Igniters,
> > >
> > > Let's discuss Thin Client Continuous Queries,
> > > I've prepared an IEP [1] and a PoC [2].
> > >
> > > [1]
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-50%3A+Thin+Client+Continuous+Queries
> > >
> > > [2] https://github.com/apache/ignite/pull/7966
> > >
> >
>

Re: IEP-50 Thin Client Continuous Queries

[Pavel Tupitsyn]

> What's about "stop" message? How can user unsubscribe from receiving
notifications?
OP_RESOURCE_CLOSE is used for that. I've updated the IEP in an attempt to
make this cleaner.

>  I've seen discussions on removing initial query from continuous queries
Interesting, I'm not aware of this. Can you please link those discussions?

On Fri, Jul 10, 2020 at 2:04 PM Igor Sapego  wrote:

> Pavel,
>
> What's about "stop" message? How can user unsubscribe from receiving
> notifications?
>
> Also, I believe I've seen discussions on removing initial query from
> continuous queries,
> as there are not any guarantees about getting consistent results with them.
> Should
> we avoid adding them in thin protocol maybe? It would also simplify
> protocol a lot.
>
> Best Regards,
> Igor
>
>
> On Tue, Jun 30, 2020 at 2:39 PM Pavel Tupitsyn 
> wrote:
>
> > Igniters,
> >
> > Let's discuss Thin Client Continuous Queries,
> > I've prepared an IEP [1] and a PoC [2].
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-50%3A+Thin+Client+Continuous+Queries
> >
> > [2] https://github.com/apache/ignite/pull/7966
> >
>

Re: IEP-50 Thin Client Continuous Queries

[Igor Sapego]

Pavel,

What's about "stop" message? How can user unsubscribe from receiving
notifications?

Also, I believe I've seen discussions on removing initial query from
continuous queries,
as there are not any guarantees about getting consistent results with them.
Should
we avoid adding them in thin protocol maybe? It would also simplify
protocol a lot.

Best Regards,
Igor


On Tue, Jun 30, 2020 at 2:39 PM Pavel Tupitsyn  wrote:

> Igniters,
>
> Let's discuss Thin Client Continuous Queries,
> I've prepared an IEP [1] and a PoC [2].
>
> [1]
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-50%3A+Thin+Client+Continuous+Queries
>
> [2] https://github.com/apache/ignite/pull/7966
>

Re: IGNITE-12362 Migrate MQTT module to ignite-extensions

[Ilya Kasnacheev]

Hello!

I have checked it, looks OK. Please note that Travis fails in ignite-ext.

Regards,
-- 
Ilya Kasnacheev


пт, 3 июл. 2020 г. в 21:50, Saikat Maitra :

> Hi
>
> I have created PRs for the following jira issue.
>
> https://issues.apache.org/jira/browse/IGNITE-12362
>
> IGNITE-12362 Migrate MQTT module to ignite-extensions
>
> PRs
> https://github.com/apache/ignite-extensions
> https://github.com/apache/ignite/pull/7950
>
>
> Please review and share your feedback.
>
> Regards,
> Saikat
>
> On Sun, Jun 21, 2020 at 3:44 PM Saikat Maitra 
> wrote:
>
> > Hi,
> >
> > I have created PRs for the following jira issue.
> >
> > https://issues.apache.org/jira/browse/IGNITE-12362
> >
> > IGNITE-12362 Migrate MQTT module to ignite-extensions
> >
> > PRs
> > https://github.com/apache/ignite-extensions
> > https://github.com/apache/ignite/pull/7950
> >
> >
> > Please review and share your feedback.
> >
> > Regards,
> > Saikat
> >
> >
> >
>

Proposal of new event QUERY_EXECUTION_EVENT

[Max Timonin]

Hi Igniters!

We're going to protocol all input SQL queries from our users. Currently
there is no such mechanism in Ignite to use for it. So we're proposing to
add a new event: QUERY_EXECUITION_EVENT.

Requirements for the event:
1. If this event fires it means that a query is correct and will be
executed (and failed only in exceptional cases);

2. Event fires for all query types;

3. Required fields are:
- text of a query (with hidden arguments);
- arguments of query;
- query type;
- node id.

Looks that this event should go along with `runningQryMgr::register` in
class `IgniteH2Indexing` as this method invoked for all input queries too.

What do you think?

Regards,
Maksim

Re: [Check Code Style] is broken in master

[Alex Plehanov]

Ivan,

Fixed. Thanks for noticing.

пт, 10 июл. 2020 г. в 15:18, Ivan Bessonov :

> Hi Igniters,
>
> today I wanted to run tests on one of my PRs and found out that master is
> broken [1].
> Issue that broked it was merged 4 hours ago and "TC Bot" VISA was
> presumably
> from the obsolete commit [2].
>
> Sergey Kalashnikov, Aleksey Plekhanov, please be careful next time.
>
> Can someone please fix it? I'm not a committer, otherwise I would do it
> myself.
>
> Fix is simple
> - org.apache.ignite.internal.processors.query.SqlNotNullKeyValueFieldTest
> class requires imports reorganization.
>
> I guess this applies to the 2.9 release branch as well.
>
> Thank you!
>
> [1]
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_CheckCodeStyle=buildTypeStatusDiv_IgniteTests24Java8=%3Cdefault%3E
> [2] https://issues.apache.org/jira/browse/IGNITE-13142
>
> --
> Sincerely yours,
> Ivan Bessonov
>

[Check Code Style] is broken in master

[Ivan Bessonov]

Hi Igniters,

today I wanted to run tests on one of my PRs and found out that master is
broken [1].
Issue that broked it was merged 4 hours ago and "TC Bot" VISA was presumably
from the obsolete commit [2].

Sergey Kalashnikov, Aleksey Plekhanov, please be careful next time.

Can someone please fix it? I'm not a committer, otherwise I would do it
myself.

Fix is simple
- org.apache.ignite.internal.processors.query.SqlNotNullKeyValueFieldTest
class requires imports reorganization.

I guess this applies to the 2.9 release branch as well.

Thank you!

[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_CheckCodeStyle=buildTypeStatusDiv_IgniteTests24Java8=%3Cdefault%3E
[2] https://issues.apache.org/jira/browse/IGNITE-13142

-- 
Sincerely yours,
Ivan Bessonov

[jira] [Created] (IGNITE-13242) LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal fails

[Ivan Bessonov (Jira)]

Ivan Bessonov created IGNITE-13242:
--

 Summary: 
LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal
 fails
 Key: IGNITE-13242
 URL: https://issues.apache.org/jira/browse/IGNITE-13242
 Project: Ignite
  Issue Type: Test
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov


[https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5966400795288779246=testDetails]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13241) Get rid of Externalizable implementation for GridCacheAdapter

[Alexey Goncharuk (Jira)]

Alexey Goncharuk created IGNITE-13241:
-

 Summary: Get rid of Externalizable implementation for 
GridCacheAdapter
 Key: IGNITE-13241
 URL: https://issues.apache.org/jira/browse/IGNITE-13241
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk


The cache implementation must not be serialized. For convenience, only user 
cache proxies support serialization.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13240) JVM Cashes on .NET Node (EXCEPTION_ACCESS_VIOLATION)

[Chris Paraskeva (Jira)]

Chris Paraskeva created IGNITE-13240:


 Summary: JVM Cashes on .NET Node (EXCEPTION_ACCESS_VIOLATION)
 Key: IGNITE-13240
 URL: https://issues.apache.org/jira/browse/IGNITE-13240
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.8.1
 Environment: OS: Windows 10

JRE version: Java(TM) SE Runtime Environment (11.0.5+10) (build 11.0.5+10-LTS)
Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0.5+10-LTS, mixed mode, tiered, 
compressed oops, g1 gc, windows-amd64)
Reporter: Chris Paraskeva


After some time of Apache Ignite is up & running using a sinle .NET Core node 
is crashing because of JAVA EXCEPTION_ACCESS_VIOLATION



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13239) Document APIs to view and change Cluster ID and Tag

[Sergey Chugunov (Jira)]

Sergey Chugunov created IGNITE-13239:


 Summary: Document APIs to view and change Cluster ID and Tag
 Key: IGNITE-13239
 URL: https://issues.apache.org/jira/browse/IGNITE-13239
 Project: Ignite
  Issue Type: Task
Reporter: Sergey Chugunov


In IGNITE-13185 new APIs and changes were introduced to view Cluster ID and Tag 
and change Tag.

These APIs and use cases need to be documented.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13238) Instant not supported whithin the scope of jdbc thin.

[Alexander Lapin (Jira)]

Alexander Lapin created IGNITE-13238:


 Summary: Instant not supported whithin the scope of jdbc thin.
 Key: IGNITE-13238
 URL: https://issues.apache.org/jira/browse/IGNITE-13238
 Project: Ignite
  Issue Type: Bug
  Components: jdbc
Affects Versions: 2.9
Reporter: Alexander Lapin


Reproducer: 
org.apache.ignite.jdbc.thin.JdbcThinCacheToJdbcDataTypesCoverageTest#testInstantDataType

 
{code:java}
[2020-07-10 
09:12:36,183][ERROR][client-connector-#196%thin.JdbcThinCacheToJdbcDataTypesCoverageTest0%][JdbcRequestHandler]
 Failed to execute SQL query [reqId=11, req=JdbcQueryExecuteRequest 
[schemaName=cachebb4b3282_3ad0_4ee3_9959_806c33521406, pageSize=1024, 
maxRows=0, sqlQry=SELECT * FROM tablebb4b3282_3ad0_4ee3_9959_806c33521406 WHERE 
_key = ?, args=Object[] [-292275055-05-16T16:47:04.192Z], 
stmtType=SELECT_STATEMENT_TYPE, autoCommit=true, partResReq=false, 
super=JdbcRequest [type=2, reqId=11]]]
javax.cache.CacheException: Failed to calculate derived partitions for query.
at 
org.apache.ignite.internal.sql.optimizer.affinity.PartitionResult.calculatePartitions(PartitionResult.java:132)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSelectDistributed(IgniteH2Indexing.java:1682)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSelect0(IgniteH2Indexing.java:1412)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSelect(IgniteH2Indexing.java:1291)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1128)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2779)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2775)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:3338)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$2(GridQueryProcessor.java:2795)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2833)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2769)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2727)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:647)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:320)
at 
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:257)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:200)
at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:54)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at 
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at 
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to wrap 
value[type=24, value=-292275055-05-16T16:47:04.192Z]
at 
org.apache.ignite.internal.processors.query.h2.H2Utils.wrap(H2Utils.java:668)
at 
org.apache.ignite.internal.processors.query.h2.H2Utils.convert(H2Utils.java:520)
at 
org.apache.ignite.internal.processors.query.h2.affinity.H2PartitionResolver.partition(H2PartitionResolver.java:43)
at 
org.apache.ignite.internal.sql.optimizer.affinity.PartitionParameterNode.applySingle(PartitionParameterNode.java:72)
at 
org.apache.ignite.internal.sql.optimizer.affinity.PartitionSingleNode.apply(PartitionSingleNode.java:47)
at 
org.apache.ignite.internal.sql.optimizer.affinity.PartitionResult.calculatePartitions(PartitionResult.java:114)
... 25 more
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)