Re: DML data streaming

[Vladimir Ozerov]

Dima,

At this point we require the following additional data which is outside of
standard SQL:
- Key type
- Value type
- Set of key columns

I do not know yet how we will define these values. At the very least we can
calculate them automatically in some cases. For "keyFieldName" and
"valFieldName" things are easier, as we can always derive them from table
definition.

Example 1 - primitives:

CREATE TABLE (
*pk_id* BIGINT PRIMARY KEY,
*val*   BIGINT
)

keyFieldName = "*pk_id*", valFieldName = "*val*"

Example 2 - composites:

CREATE TABLE (
*pk_id* BIGINT PRIMARY KEY,
val1  BIGINT,
val2  VARCHAR
)

keyFieldName = "*pk_id*", valFieldName = null (because value is complex and
is composed of two attributes).

Vladimir.


On Wed, Feb 15, 2017 at 11:42 PM, Dmitriy Setrakyan 
wrote:

> On Wed, Feb 15, 2017 at 4:28 AM, Vladimir Ozerov 
> wrote:
>
> > Ok, let's put aside current fields configuration, I'll create separate
> > thread for it. As far as _KEY and _VAL, proposed change is exactly about
> > mappings:
> >
> > class QueryEntity {
> > ...
> > String keyFieldName;
> > String valFieldName;
> > ...
> > }
> >
> > The key thing is that we will not require users to be aware of our system
> > columns. Normally user should not bother about existence of hidden _KEY
> and
> > _VAL columns. Instead, we just allow them to optionally reference the
> whole
> > key and/or val through predefined name.
> >
> >
> Vladimir, how will it work from the DDL perspective. Let's say whenever
> user wants to create a table in Ignite?
>

IGNITE-2626 Binary marshaller: sort fields alphabetically

[ALEKSEY KUZNETSOV]

im going to take https://issues.apache.org/jira/browse/IGNITE-2626
-- 

*Best Regards,*

*Kuznetsov Aleksey*

Re: IGNITE-2626 Binary marshaller: sort fields alphabetically

[Vyacheslav Daradur]

Hello.

Look at the ticket: https://issues.apache.org/jira/browse/IGNITE-4695
- Write primitive fields before during binary object marshalling

Maybe it relates.

2017-02-16 11:18 GMT+03:00 ALEKSEY KUZNETSOV :

> im going to take https://issues.apache.org/jira/browse/IGNITE-2626
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

[Alexey Kuznetsov]

Hi!

I did minor code-style review directly on GitHub. Please fix.

But some one who knows GridCacheProcessor.java should do one more review.

On Thu, Feb 16, 2017 at 2:38 PM, ALEKSEY KUZNETSOV  wrote:

> Plz, review my PR : https://github.com/apache/ignite/pull/1517
>
> https://issues.apache.org/jira/browse/IGNITE-1178
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>



-- 
Alexey Kuznetsov

Re: IGNITE-2626 Binary marshaller: sort fields alphabetically

[ALEKSEY KUZNETSOV]

yeap

чт, 16 февр. 2017 г. в 11:26, Vyacheslav Daradur :

> Hello.
>
> Look at the ticket: https://issues.apache.org/jira/browse/IGNITE-4695
> - Write primitive fields before during binary object marshalling
>
> Maybe it relates.
>
> 2017-02-16 11:18 GMT+03:00 ALEKSEY KUZNETSOV :
>
> > im going to take https://issues.apache.org/jira/browse/IGNITE-2626
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
> >
>
-- 

*Best Regards,*

*Kuznetsov Aleksey*

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

[ALEKSEY KUZNETSOV]

thankx

чт, 16 февр. 2017 г. в 11:29, Alexey Kuznetsov :

> Hi!
>
> I did minor code-style review directly on GitHub. Please fix.
>
> But some one who knows GridCacheProcessor.java should do one more review.
>
> On Thu, Feb 16, 2017 at 2:38 PM, ALEKSEY KUZNETSOV <
> alkuznetsov...@gmail.com
> > wrote:
>
> > Plz, review my PR : https://github.com/apache/ignite/pull/1517
> >
> > https://issues.apache.org/jira/browse/IGNITE-1178
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
> >
>
>
>
> --
> Alexey Kuznetsov
>
-- 

*Best Regards,*

*Kuznetsov Aleksey*

[jira] [Created] (IGNITE-4708) Web Console: Show detailed information about error on Queries screen

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-4708:


 Summary: Web Console: Show detailed information about error on 
Queries screen
 Key: IGNITE-4708
 URL: https://issues.apache.org/jira/browse/IGNITE-4708
 Project: Ignite
  Issue Type: Task
  Components: UI, wizards
Affects Versions: 1.8
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.0


In current implementation Web Console shows only top messages from stack trace 
and usually looks like "Failed to parse bla-bla".

We need to show full stack trace with all errors.
Show some troubleshooting tips for user to help him to fix query, for example, 
select correct cache.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4709) Web Console: Implement support for Affinity key configuration on Model screen

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-4709:


 Summary: Web Console: Implement support for Affinity key 
configuration on Model screen
 Key: IGNITE-4709
 URL: https://issues.apache.org/jira/browse/IGNITE-4709
 Project: Ignite
  Issue Type: Task
  Components: UI, wizards
Affects Versions: 1.8
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.0


Web Console should give possibility to configure Affinity key visually and 
generate appropriate XML and Java code.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Implement IgniteZeromqStreamer to stream data from ZeroMQ

[Kozlov Maxim]

Hello Igniters,

Please review and comment implementation ZeroMQ streamer.
PR: https://github.com/apache/ignite/pull/1532 

Jira: https://issues.apache.org/jira/browse/IGNITE-533 



--
Best Regards,
Max K.

Re: IGNITE-602

[Vladimir Ozerov]

Hi Dmitriy,

We should print all objects, because this is the whole purpose of
GridToStringBuilder class - to print as much as possible in pretty format.
For cyclic references, we should introduce smarter approach, ensuring that
certain object is printed only once, I would use a kind of stack or
IdentityHashMap to track already printed entries and then print a reference
to them instead of the whole body.

We use similar approach for binary objects, see
BinaryObjectExImpl.toString(...)
method. In this case (hash + body) is printed normally, but when a cycle is
found, we print only (hash). This is not very suitable for
GridToStringBuilder, as we definitely do not want output to be flooded with
hashes, which are useless in common case. May be it makes sense to object's
position in already printed string.

Vladimir.


On Wed, Feb 15, 2017 at 3:07 PM, Дмитрий Рябов 
wrote:

> Hello, can you answer me a simple question?
>
> We have 2 looping lists:
>
> ArrayList list1 = new ArrayList<>();
> ArrayList list2 = new ArrayList<>();
>
> list2.add(list1);
> list1.add(list2);
>
> Class GridToStringBuilder represent them into string.
>
> Simple public static  String toString(Class cls, T obj) method
> returns string "ArrayList [size=1]" for each list.
>
> *Question is* how should look the result of toString(Class cls, T obj,
> String name, @Nullable Object val) method and other methods with additional
> values?
> "ArrayList [size=1, name=ArrayList[size=1]]" or something else?
>
> The trouble is in GridStringBuilder.a(Object obj) method - it tries to
> append collection's toString() method which invokes toString() on every
> element.
>

IGNITE-1624: [Test failed] Ignite SPI: TcpClientDiscoverySpiSelfTest.testJoinError failed

[Александр Меньшиков]

Hello.

I try to fix test. But can't reproduce problem. I added reps in a loop and
ran test local 10 minutes. There aren't problem. After that I set 1500 reps
and ran on CI (my local machine can do 1900 reps in 5 minutes) and got
timeout, but not the origin problem from issue.

Anyone have any ideas on how to reproduce the problem?

[jira] [Created] (IGNITE-4710) Better optimistic tx lock conflict client information.

[Stanilovsky Evgeny (JIRA)]

Stanilovsky Evgeny created IGNITE-4710:
--

 Summary: Better optimistic tx lock conflict client information.
 Key: IGNITE-4710
 URL: https://issues.apache.org/jira/browse/IGNITE-4710
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 1.8
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
Priority: Minor


On tx optimistic exception we should provide information about key causing 
conflict for easier debugging of conflict source.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1540: Ignite 4710

[zstan]

GitHub user zstan opened a pull request:

https://github.com/apache/ignite/pull/1540

Ignite 4710



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4710

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1540.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1540


commit 71d69408e78a781f64f99c9ab75fec0c36c422ea
Author: Dmitriy Govorukhin 
Date:   2016-12-05T16:28:33Z

ignite-gg-11650  destroy all cache if activation fail

commit 1eb73d952f740305ec37e37efa0c5333fc2dd032
Author: Ilya Lantukh 
Date:   2016-12-05T16:37:54Z

gg-11730 : Fixed inconsistency between data and indexes caused by updates 
while node is stopping.

commit 806e41d14a81d7f3cc51384071a4d6c3428ef899
Author: Dmitriy Govorukhin 
Date:   2016-12-05T16:50:49Z

ignite-gg-11650  destroy all cache if activation fail (fix test fail)

commit dda12750387de278b2ca91aa6d466d28f78e9293
Author: devozerov 
Date:   2016-11-24T08:14:08Z

IGNITE-4270: Allow GridUnsafe.UNALIGNED flag override.

commit e657456e13698bcb3784bf3ee77e1f85785d8968
Author: devozerov 
Date:   2016-11-25T08:22:05Z

IGNITE-4270: Fixed system property name.

commit 09ccb7052ebbfd486dfdb835c8d9ff7813ef94ba
Author: EdShangGG 
Date:   2016-12-05T16:58:44Z

Revert Partitioned index - WIP.

commit a0dd3d93cab1bb076898f47ff09fcf1e9533b90a
Author: Dmitriy Govorukhin 
Date:   2016-12-05T17:09:45Z

ignite-gg-11650  add deployId for deactivate caches

commit 81ee8c01b8dec8e21106db8c6712883dfd4263f2
Author: EdShangGG 
Date:   2016-12-06T09:19:16Z

Merge remote-tracking branch 'origin/ignite-gg-8.0.1.ea7' into 
ignite-db-x-backup-idx

commit cf9bbaaa38368dce2fa07cfa55900e9e3df8b4b3
Author: Alexey Goncharuk 
Date:   2016-12-06T12:14:03Z

Merge gg-11721 ignite-gg-8.0.1.ea7

commit 639aa92479083f1e692479182e9f6b2c610254ef
Author: Alexey Goncharuk 
Date:   2016-12-06T12:14:40Z

Merge gg-11721 ignite-gg-8.0.1.ea7 (minor)

commit 3ac945c78a839e825063bf11f06192fdd01c8b31
Author: Ilya Lantukh 
Date:   2016-12-06T15:39:13Z

gg-11730 : Minors.

commit 8b9df7a3a2a5b8d318194f37aff71fa7939011a8
Author: Ilya Lantukh 
Date:   2016-12-06T15:40:03Z

gg-11708 : Minors.

commit 3371cebf1095a8d033e987c63e6040bec28f0dfd
Author: Ilya Lantukh 
Date:   2016-12-06T16:08:50Z

Merge branches 'ignite-gg-11708' and 'ignite-gg-8.0.1.ea7' of 
https://github.com/gridgain/apache-ignite into ignite-gg-11708

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtPartitionTopologyImpl.java

Merge branches 'ignite-gg-11708' and 'ignite-gg-8.0.1.ea7' of 
https://github.com/ggprivate/ggprivate into ignite-gg-11708

# Conflicts:
#   
modules/core/src/main/java/org/gridgain/grid/internal/processors/cache/database/pagemem/FullPageIdTable.java
#   
modules/pds/src/main/java/org/gridgain/grid/internal/processors/cache/database/GridCacheDatabaseSharedManager.java

commit f308cd87b2eee0c81768783de531783c623ef396
Author: Dmitriy Govorukhin 
Date:   2016-12-06T16:41:00Z

ignite-gg-11650  refactoring + failover tests

commit 1e5bb0ad36aa010fa0801b6f534ba4fe7f5b0c8c
Author: Alexey Goncharuk 
Date:   2016-12-07T08:55:07Z

Do not call assignPartitionStates() for local caches

commit 90986022d30bc03529a77d94c5373149b023d23b
Author: Dmitriy Govorukhin 
Date:   2016-12-07T09:26:57Z

ignite-gg-11650  cleaning activation context

commit a7c4482876661ccda7e183f20b5b4632221e455f
Author: Dmitriy Govorukhin 
Date:   2016-12-07T10:20:59Z

ignite-gg-11650  small update fro clearing act context

commit 68fc7f7666c50f75e05eda758d0f03e15f3026cd
Author: Alexey Kuznetsov 
Date:   2016-12-07T11:58:45Z

GG-11738 Implemented UI for activate/deactivate cluster.

commit 991eff2372fcd422b5941f01c80a9b4249e02ba6
Author: EdShangGG 
Date:   2016-12-07T17:56:50Z

GG-11688 Extend Backup SPI to get information about backup from whole 
cluster
-tests pass
-API changes

commit e05ea2fc1009f783572d9cabba80ebf0f6fbb6da
Author: Alexey Kuznetsov 
Date:   2016-12-08T10:45:26Z

Updated classnames.properties to run from IDE.

commit 7389c1bbd42b1601883ec4952459dd5882154d3f
Author: Ilya Lantukh 
Date:   2016-12-08T12:25:17Z

Merge branches 'ignite-gg-11730' and 'ignite-gg-8.0.1.ea7' of 
https://github.com/gridgain/apache-ignite into ignite-gg-8.0.1.ea7

commit b75c1ca32ec41715a69b59bceeb65c9e9cdd7050
Author: Ilya Lantukh 
Date:   2016-12-08T13:15:42Z

Fixed index consistency.

commit 1b6402fd2cc674f736319e84e50f769768b89a27
Author: EdShangGG 
Date:   2016-12-08T13:49:50Z

GG-11688 Extend Backup SPI to get information about backup from whole 
cluster
-new tests
-new checks while snapshot restore
-refactorings

commit 6d781b7

Re: error - Failed to wait for partition release future

[Andrey Mashenkov]

Hi Cameron,

Ignite does not have 1.8.x versions.

It look like you use IPv6 on some of you nodes.
At first, check if either -Djava.net.preferIPv6Addresses=true or
-Djava.net.preferIPv4Addresses=true java option is set for all of your
nodes
and communication port is set properly.

On Thu, Feb 16, 2017 at 1:29 AM, Cameron Braid  wrote:

> Hi,
>
> I am getting the following error in Ignite version 1.8.1 :
>
> "Failed to wait for partition release future"
>
> The related logs lines are at the bottom.
>
> I was curious if it could be related to
> https://issues.apache.org/jira/browse/IGNITE-3212 which has fix for
> version
> 1.9.  Could this be the case ?
>
> Otherwise, is this likely to be a bug in ignite, or something specific to
> my environment?
>
> Cheers
>
> Cameron
>
>
>- Feb 16 08:23:28 webapp-92-50ik3 webapp 15287661 WARN
>o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture
>[exchange-worker-#26%webapp%] Failed to wait for partition release
> future
>[topVer=AffinityTopologyVersion [topVer=21, minorTopVer=2],
>node=79d74dfa-9903-42e3-af94-524ab08c1f97]. Dumping pending objects
> that
>might be the cause:
>- Feb 16 08:23:28 webapp-92-50ik3 webapp 15287661 WARN
>o.a.i.i.p.c.GridCachePartitionExchangeManager
>[exchange-worker-#26%webapp%] Ready affinity version:
>AffinityTopologyVersion [topVer=21, minorTopVer=1]
>- Feb 16 08:23:28 webapp-92-50ik3 webapp 15287667 WARN
>o.a.i.i.p.c.GridCachePartitionExchangeManager
>[exchange-worker-#26%webapp%] Last exchange future:
>GridDhtPartitionsExchangeFuture [dummy=false, forcePreload=false,
>reassign=false, discoEvt=DiscoveryCustomEvent
>[customMsg=DynamicCacheChangeBatch [reqs=[DynamicCacheChangeRequest
>[deploymentId=3f757f24a51-ee74fcc5-5cea-4548-9cd6-8a201c29fdf9,
>startCfg=CacheConfiguration [name=userTable.cmsDataVehicles.query,
>storeConcurrentLoadAllThreshold=5, rebalancePoolSize=2,
>rebalanceTimeout=1, evictPlc=null, evictSync=false,
>evictKeyBufSize=1024, evictSyncConcurrencyLvl=4, evictSyncTimeout=1,
>evictFilter=null, evictMaxOverflowRatio=10.0, eagerTtl=true,
>dfltLockTimeout=0, startSize=150, nearCfg=null,
> writeSync=PRIMARY_SYNC,
>storeFactory=null, storeKeepBinary=false, loadPrevVal=false,
>aff=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction@7e1c4f4,
>cacheMode=REPLICATED, atomicityMode=ATOMIC,
> atomicWriteOrderMode=PRIMARY,
>backups=2147483647, invalidate=false, tmLookupClsName=null,
>rebalanceMode=ASYNC, rebalanceOrder=0, rebalanceBatchSize=524288,
>rebalanceBatchesPrefetchCount=2, offHeapMaxMem=-1, swapEnabled=false,
>maxConcurrentAsyncOps=500, writeBehindEnabled=false,
>writeBehindFlushSize=10240, writeBehindFlushFreq=5000,
>writeBehindFlushThreadCnt=1, writeBehindBatchSize=512,
> maxQryIterCnt=1024,
>memMode=ONHEAP_TIERED,
>affMapper=o.a.i.i.processors.cache.CacheDefaultBinaryAffinityKeyM
> apper@6ca896dd,
>rebalanceDelay=0, rebalanceThrottle=0, interceptor=null,
>longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true,
>nodeFilter=o.a.i.configuration.CacheConfiguration$
> IgniteAllNodesPredicate@db2015b,
>sqlSchema=null, sqlEscapeAll=false, sqlOnheapRowCacheSize=10240,
>snapshotableIdx=false, cpOnRead=true, topValidator=null],
> cacheType=USER,
>initiatingNodeId=79d74dfa-9903-42e3-af94-524ab08c1f97,
> nearCacheCfg=null,
>clientStartOnly=false, stop=false, close=false, failIfExists=true,
>template=false, rcvdFrom=null, exchangeNeeded=true, cacheFutTopVer=null,
>cacheName=userTable.cmsDataVehicles.query]], clientNodes=null,
>id=4f757f24a51-ee74fcc5-5cea-4548-9cd6-8a201c29fdf9,
>clientReconnect=false], affTopVer=AffinityTopologyVersion [topVer=21,
>minorTopVer=2], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
>[id=79d74dfa-9903-42e3-af94-524ab08c1f97, addrs=[0:0:0:0:0:0:0:1%lo,
>10.130.1.43, 127.0.0.1], sockAddrs=[webapp-92-50ik3/10.130.1.43:47500,
>/0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500], discPort=47500, order=21,
>intOrder=12, lastExchangeTime=1487193806549, loc=true,
>ver=1.8.1#20161208-sha1:a8fcb7b2, isClient=false], topVer=21,
>nodeId8=79d74dfa, msg=null, type=DISCOVERY_CUSTOM_EVT,
>tstamp=1487193798024]], crd=TcpDiscoveryNode
>[id=659ea029-ca80-4413-af47-67b446ffd3e7, addrs=[0:0:0:0:0:0:0:1%lo,
>10.128.1.11, 127.0.0.1], sockAddrs=[/0:0:0:0:0:0:0:1%lo:47500, /
>127.0.0.1:47500, /10.128.1.11:47500], discPort=47500, order=18,
>intOrder=10, lastExchangeTime=1487178534506, loc=false,
>ver=1.8.1#20161208-sha1:a8fcb7b2, isClient=false],
>exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion
>[topVer=21, minorTopVer=2], nodeId=79d74dfa, evt=DISCOVERY_CUSTOM_EVT],
>added=true, initFut=GridFutureAdapter [resFlag=0, res=null,
>startTime=1487193798024, endTime=0, ignoreInterrupts=false, state=INIT],
>init=false, topSnapshot=null, lastVer=null,
>par

[GitHub] ignite pull request #1540: Ignite 4710

[zstan]

Github user zstan closed the pull request at:

https://github.com/apache/ignite/pull/1540


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1541: Ignite 4710

[zstan]

GitHub user zstan opened a pull request:

https://github.com/apache/ignite/pull/1541

Ignite 4710



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite IGNITE-4710

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1541.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1541


commit 71d69408e78a781f64f99c9ab75fec0c36c422ea
Author: Dmitriy Govorukhin 
Date:   2016-12-05T16:28:33Z

ignite-gg-11650  destroy all cache if activation fail

commit 1eb73d952f740305ec37e37efa0c5333fc2dd032
Author: Ilya Lantukh 
Date:   2016-12-05T16:37:54Z

gg-11730 : Fixed inconsistency between data and indexes caused by updates 
while node is stopping.

commit 806e41d14a81d7f3cc51384071a4d6c3428ef899
Author: Dmitriy Govorukhin 
Date:   2016-12-05T16:50:49Z

ignite-gg-11650  destroy all cache if activation fail (fix test fail)

commit dda12750387de278b2ca91aa6d466d28f78e9293
Author: devozerov 
Date:   2016-11-24T08:14:08Z

IGNITE-4270: Allow GridUnsafe.UNALIGNED flag override.

commit e657456e13698bcb3784bf3ee77e1f85785d8968
Author: devozerov 
Date:   2016-11-25T08:22:05Z

IGNITE-4270: Fixed system property name.

commit 09ccb7052ebbfd486dfdb835c8d9ff7813ef94ba
Author: EdShangGG 
Date:   2016-12-05T16:58:44Z

Revert Partitioned index - WIP.

commit a0dd3d93cab1bb076898f47ff09fcf1e9533b90a
Author: Dmitriy Govorukhin 
Date:   2016-12-05T17:09:45Z

ignite-gg-11650  add deployId for deactivate caches

commit 81ee8c01b8dec8e21106db8c6712883dfd4263f2
Author: EdShangGG 
Date:   2016-12-06T09:19:16Z

Merge remote-tracking branch 'origin/ignite-gg-8.0.1.ea7' into 
ignite-db-x-backup-idx

commit cf9bbaaa38368dce2fa07cfa55900e9e3df8b4b3
Author: Alexey Goncharuk 
Date:   2016-12-06T12:14:03Z

Merge gg-11721 ignite-gg-8.0.1.ea7

commit 639aa92479083f1e692479182e9f6b2c610254ef
Author: Alexey Goncharuk 
Date:   2016-12-06T12:14:40Z

Merge gg-11721 ignite-gg-8.0.1.ea7 (minor)

commit 3ac945c78a839e825063bf11f06192fdd01c8b31
Author: Ilya Lantukh 
Date:   2016-12-06T15:39:13Z

gg-11730 : Minors.

commit 8b9df7a3a2a5b8d318194f37aff71fa7939011a8
Author: Ilya Lantukh 
Date:   2016-12-06T15:40:03Z

gg-11708 : Minors.

commit 3371cebf1095a8d033e987c63e6040bec28f0dfd
Author: Ilya Lantukh 
Date:   2016-12-06T16:08:50Z

Merge branches 'ignite-gg-11708' and 'ignite-gg-8.0.1.ea7' of 
https://github.com/gridgain/apache-ignite into ignite-gg-11708

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtPartitionTopologyImpl.java

Merge branches 'ignite-gg-11708' and 'ignite-gg-8.0.1.ea7' of 
https://github.com/ggprivate/ggprivate into ignite-gg-11708

# Conflicts:
#   
modules/core/src/main/java/org/gridgain/grid/internal/processors/cache/database/pagemem/FullPageIdTable.java
#   
modules/pds/src/main/java/org/gridgain/grid/internal/processors/cache/database/GridCacheDatabaseSharedManager.java

commit f308cd87b2eee0c81768783de531783c623ef396
Author: Dmitriy Govorukhin 
Date:   2016-12-06T16:41:00Z

ignite-gg-11650  refactoring + failover tests

commit 1e5bb0ad36aa010fa0801b6f534ba4fe7f5b0c8c
Author: Alexey Goncharuk 
Date:   2016-12-07T08:55:07Z

Do not call assignPartitionStates() for local caches

commit 90986022d30bc03529a77d94c5373149b023d23b
Author: Dmitriy Govorukhin 
Date:   2016-12-07T09:26:57Z

ignite-gg-11650  cleaning activation context

commit a7c4482876661ccda7e183f20b5b4632221e455f
Author: Dmitriy Govorukhin 
Date:   2016-12-07T10:20:59Z

ignite-gg-11650  small update fro clearing act context

commit 68fc7f7666c50f75e05eda758d0f03e15f3026cd
Author: Alexey Kuznetsov 
Date:   2016-12-07T11:58:45Z

GG-11738 Implemented UI for activate/deactivate cluster.

commit 991eff2372fcd422b5941f01c80a9b4249e02ba6
Author: EdShangGG 
Date:   2016-12-07T17:56:50Z

GG-11688 Extend Backup SPI to get information about backup from whole 
cluster
-tests pass
-API changes

commit e05ea2fc1009f783572d9cabba80ebf0f6fbb6da
Author: Alexey Kuznetsov 
Date:   2016-12-08T10:45:26Z

Updated classnames.properties to run from IDE.

commit 7389c1bbd42b1601883ec4952459dd5882154d3f
Author: Ilya Lantukh 
Date:   2016-12-08T12:25:17Z

Merge branches 'ignite-gg-11730' and 'ignite-gg-8.0.1.ea7' of 
https://github.com/gridgain/apache-ignite into ignite-gg-8.0.1.ea7

commit b75c1ca32ec41715a69b59bceeb65c9e9cdd7050
Author: Ilya Lantukh 
Date:   2016-12-08T13:15:42Z

Fixed index consistency.

commit 1b6402fd2cc674f736319e84e50f769768b89a27
Author: EdShangGG 
Date:   2016-12-08T13:49:50Z

GG-11688 Extend Backup SPI to get information about backup from whole 
cluster
-new tests
-new checks while snapshot restore
-refactorings

commit 6d781b7

Re: IGNITE-602

[Дмитрий Рябов]

Hello, Vladimir. Do you mean something like "ArrayList [size=1,
name=ArrayList [size=1, ArrayList {position 0}]]"?

2017-02-16 12:32 GMT+03:00 Vladimir Ozerov :

> Hi Dmitriy,
>
> We should print all objects, because this is the whole purpose of
> GridToStringBuilder class - to print as much as possible in pretty format.
> For cyclic references, we should introduce smarter approach, ensuring that
> certain object is printed only once, I would use a kind of stack or
> IdentityHashMap to track already printed entries and then print a reference
> to them instead of the whole body.
>
> We use similar approach for binary objects, see
> BinaryObjectExImpl.toString(...)
> method. In this case (hash + body) is printed normally, but when a cycle is
> found, we print only (hash). This is not very suitable for
> GridToStringBuilder, as we definitely do not want output to be flooded with
> hashes, which are useless in common case. May be it makes sense to object's
> position in already printed string.
>
> Vladimir.
>
>
> On Wed, Feb 15, 2017 at 3:07 PM, Дмитрий Рябов 
> wrote:
>
> > Hello, can you answer me a simple question?
> >
> > We have 2 looping lists:
> >
> > ArrayList list1 = new ArrayList<>();
> > ArrayList list2 = new ArrayList<>();
> >
> > list2.add(list1);
> > list1.add(list2);
> >
> > Class GridToStringBuilder represent them into string.
> >
> > Simple public static  String toString(Class cls, T obj) method
> > returns string "ArrayList [size=1]" for each list.
> >
> > *Question is* how should look the result of toString(Class cls, T obj,
> > String name, @Nullable Object val) method and other methods with
> additional
> > values?
> > "ArrayList [size=1, name=ArrayList[size=1]]" or something else?
> >
> > The trouble is in GridStringBuilder.a(Object obj) method - it tries to
> > append collection's toString() method which invokes toString() on every
> > element.
> >
>

Re: Apache Ignite 1.9

[Anton Vinogradov]

Denis,

Evgenii Zhuravlev going to fix this issue. I'll provide him help if
necessarry.

On Wed, Feb 15, 2017 at 8:03 PM, Denis Magda  wrote:

> Anton,
>
> The implementation is correct and was reviewed by Val long time ago. The
> only issue that is left is the compilation in *TeamCity* only.
> You fixed it for one scala version and now should simply do the same for
> other scala version by adding a new suite to TeamCity and adjusting the pom.
>
> —
> Denis
>
> > On Feb 15, 2017, at 1:20 AM, Anton Vinogradov 
> wrote:
> >
> > Denis,
> >
> > I don't know what is the plan for this issue.
> > You asked me to fix compilation and thats what I done :) , but I'm not
> sure
> > that issue implemented in proper way. I don't like changes I've done,
> they
> > looks redundant although it works.
> > Do we have somebody more familiar with spark inside the community?
> > We have to review what we already done and figure out what's left.
> >
> > On Wed, Feb 15, 2017 at 5:01 AM, Denis Magda  wrote:
> >
> >> Continuing Spark related topic...
> >>
> >> This ticket definitely must be included in 1.9:
> >> https://issues.apache.org/jira/browse/IGNITE-3710 <
> >> https://issues.apache.org/jira/browse/IGNITE-3710>
> >>
> >> We can’t longer afford torture Ignite Shared RDD users who have to use
> an
> >> outdated Spark version.
> >>
> >> Anton, could you finalize it this week? As far as I remember, the only
> >> thing that is left is to add a missing test suite to Team City.
> >>
> >> —
> >> Denis
> >>
> >>> On Feb 14, 2017, at 5:00 PM, Denis Magda  wrote:
> >>>
> >>> Reviewed and merged the first (!) Ignite Shared RDD examples
> contributed
> >> by Manish:
> >>>
> >>> https://issues.apache.org/jira/browse/IGNITE-4526
> >>>
> >>> Java:
> >>> https://github.com/apache/ignite/blob/b461cb47882861356ede58775bd9e2
> >> 53dcf26202/examples/src/main/java8/org/apache/ignite/
> examples/java8/spark/
> >> SharedRDDExample.java
> >>>
> >>> Scala:
> >>> https://github.com/apache/ignite/blob/b461cb47882861356ede58775bd9e2
> >> 53dcf26202/examples/src/main/scala/org/apache/ignite/
> >> scalar/examples/spark/ScalarSharedRDDExample.scala
> >>>
> >>> Manish, thanks for making the life of Apache Ignite users easier. No
> >> they can refer to your examples while learning Ignite Shared RDD API.
> >>>
> >>> —
> >>> Denis
> >>>
>  On Feb 14, 2017, at 1:21 AM, Anton Vinogradov <
> avinogra...@gridgain.com>
> >> wrote:
> 
> >
> > Can we push to 1.9 and then merge/rebase to master?
> 
> 
>  Yes, that's *correct *too, but only *megre *should be used.
> 
>  On Tue, Feb 14, 2017 at 12:19 PM, Vladimir Ozerov <
> voze...@gridgain.com
> >>>
>  wrote:
> 
> > Can we push to 1.9 and then merge/rebase to master? It should be more
> > reliable than cherry-picking.
> >
> > On Tue, Feb 14, 2017 at 12:15 PM, Anton Vinogradov <
> > avinogra...@gridgain.com
> >> wrote:
> >
> >> Denis,
> >>
> >> Merge to the master first and then cherry-pick to 1.9 from there is
> a
> >> *correct
> >> *case.
> >>
> >> On Tue, Feb 14, 2017 at 5:24 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org>
> >> wrote:
> >>
> >>> Thanks, Denis!
> >>>
> >>> On Mon, Feb 13, 2017 at 5:49 PM, Denis Magda 
> > wrote:
> >>>
>  Well, merged Kubernetes integration to the master and
> cherry-picked
> > to
>  1.9. The docs and getting started for readme.io to be done soon.
> 
>  —
>  Denis
> 
> > On Feb 13, 2017, at 9:10 AM, Denis Magda 
> > wrote:
> >
> > Do I merge to the master first and then cherry-pick to 1.9 from
> >> there?
> >
> > —
> > Denis
> >
> >> On Feb 13, 2017, at 8:21 AM, Anton Vinogradov <
> >>> avinogra...@gridgain.com>
>  wrote:
> >>
> >> Igniters,
> >>
> >> We're starting release stabilization process.
> >> Branch 1.9 created and equals to master branch right now.
> >>
> >> Please make sure that your changes will be merged to both
> > branches:
> >> *ignite-1.9* and *master*.
> >>
> >> On Fri, Feb 10, 2017 at 4:53 PM, Sergey Kalashnikov <
>  zkilling...@gmail.com>
> >> wrote:
> >>
> >>> Anton,
> >>>
> >>> Here is the status for IGNITE-4523.
> >>> The work is completed, tests are OK.
> >>> Most of the changes were made by Alexey and were reviewed.
> >>> I only authored few last commits for which I would appreciate a
> >>> review.
> >>> The PR is https://github.com/apache/ignite/pull/1508
> >>>
> >>> Thank you
> >>> --
> >>> Sergey
> >>>
> >>>
> >>>
> >>> 2017-02-09 23:58 GMT+03:00 Denis Magda :
> >>>
>  Anton,
> 
>  You can expect Kubernetes support from 

[GitHub] ignite pull request #1541: IGNITE-4710 extended optimistic tx lock conflict ...

[zstan]

Github user zstan closed the pull request at:

https://github.com/apache/ignite/pull/1541


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1542: IGNITE-4710 extended optimistic tx lock conflict ...

[zstan]

GitHub user zstan opened a pull request:

https://github.com/apache/ignite/pull/1542

IGNITE-4710 extended optimistic tx lock conflict exception message 



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4710

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1542.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1542


commit 71d69408e78a781f64f99c9ab75fec0c36c422ea
Author: Dmitriy Govorukhin 
Date:   2016-12-05T16:28:33Z

ignite-gg-11650  destroy all cache if activation fail

commit 1eb73d952f740305ec37e37efa0c5333fc2dd032
Author: Ilya Lantukh 
Date:   2016-12-05T16:37:54Z

gg-11730 : Fixed inconsistency between data and indexes caused by updates 
while node is stopping.

commit 806e41d14a81d7f3cc51384071a4d6c3428ef899
Author: Dmitriy Govorukhin 
Date:   2016-12-05T16:50:49Z

ignite-gg-11650  destroy all cache if activation fail (fix test fail)

commit dda12750387de278b2ca91aa6d466d28f78e9293
Author: devozerov 
Date:   2016-11-24T08:14:08Z

IGNITE-4270: Allow GridUnsafe.UNALIGNED flag override.

commit e657456e13698bcb3784bf3ee77e1f85785d8968
Author: devozerov 
Date:   2016-11-25T08:22:05Z

IGNITE-4270: Fixed system property name.

commit 09ccb7052ebbfd486dfdb835c8d9ff7813ef94ba
Author: EdShangGG 
Date:   2016-12-05T16:58:44Z

Revert Partitioned index - WIP.

commit a0dd3d93cab1bb076898f47ff09fcf1e9533b90a
Author: Dmitriy Govorukhin 
Date:   2016-12-05T17:09:45Z

ignite-gg-11650  add deployId for deactivate caches

commit 81ee8c01b8dec8e21106db8c6712883dfd4263f2
Author: EdShangGG 
Date:   2016-12-06T09:19:16Z

Merge remote-tracking branch 'origin/ignite-gg-8.0.1.ea7' into 
ignite-db-x-backup-idx

commit cf9bbaaa38368dce2fa07cfa55900e9e3df8b4b3
Author: Alexey Goncharuk 
Date:   2016-12-06T12:14:03Z

Merge gg-11721 ignite-gg-8.0.1.ea7

commit 639aa92479083f1e692479182e9f6b2c610254ef
Author: Alexey Goncharuk 
Date:   2016-12-06T12:14:40Z

Merge gg-11721 ignite-gg-8.0.1.ea7 (minor)

commit 3ac945c78a839e825063bf11f06192fdd01c8b31
Author: Ilya Lantukh 
Date:   2016-12-06T15:39:13Z

gg-11730 : Minors.

commit 8b9df7a3a2a5b8d318194f37aff71fa7939011a8
Author: Ilya Lantukh 
Date:   2016-12-06T15:40:03Z

gg-11708 : Minors.

commit 3371cebf1095a8d033e987c63e6040bec28f0dfd
Author: Ilya Lantukh 
Date:   2016-12-06T16:08:50Z

Merge branches 'ignite-gg-11708' and 'ignite-gg-8.0.1.ea7' of 
https://github.com/gridgain/apache-ignite into ignite-gg-11708

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtPartitionTopologyImpl.java

Merge branches 'ignite-gg-11708' and 'ignite-gg-8.0.1.ea7' of 
https://github.com/ggprivate/ggprivate into ignite-gg-11708

# Conflicts:
#   
modules/core/src/main/java/org/gridgain/grid/internal/processors/cache/database/pagemem/FullPageIdTable.java
#   
modules/pds/src/main/java/org/gridgain/grid/internal/processors/cache/database/GridCacheDatabaseSharedManager.java

commit f308cd87b2eee0c81768783de531783c623ef396
Author: Dmitriy Govorukhin 
Date:   2016-12-06T16:41:00Z

ignite-gg-11650  refactoring + failover tests

commit 1e5bb0ad36aa010fa0801b6f534ba4fe7f5b0c8c
Author: Alexey Goncharuk 
Date:   2016-12-07T08:55:07Z

Do not call assignPartitionStates() for local caches

commit 90986022d30bc03529a77d94c5373149b023d23b
Author: Dmitriy Govorukhin 
Date:   2016-12-07T09:26:57Z

ignite-gg-11650  cleaning activation context

commit a7c4482876661ccda7e183f20b5b4632221e455f
Author: Dmitriy Govorukhin 
Date:   2016-12-07T10:20:59Z

ignite-gg-11650  small update fro clearing act context

commit 68fc7f7666c50f75e05eda758d0f03e15f3026cd
Author: Alexey Kuznetsov 
Date:   2016-12-07T11:58:45Z

GG-11738 Implemented UI for activate/deactivate cluster.

commit 991eff2372fcd422b5941f01c80a9b4249e02ba6
Author: EdShangGG 
Date:   2016-12-07T17:56:50Z

GG-11688 Extend Backup SPI to get information about backup from whole 
cluster
-tests pass
-API changes

commit e05ea2fc1009f783572d9cabba80ebf0f6fbb6da
Author: Alexey Kuznetsov 
Date:   2016-12-08T10:45:26Z

Updated classnames.properties to run from IDE.

commit 7389c1bbd42b1601883ec4952459dd5882154d3f
Author: Ilya Lantukh 
Date:   2016-12-08T12:25:17Z

Merge branches 'ignite-gg-11730' and 'ignite-gg-8.0.1.ea7' of 
https://github.com/gridgain/apache-ignite into ignite-gg-8.0.1.ea7

commit b75c1ca32ec41715a69b59bceeb65c9e9cdd7050
Author: Ilya Lantukh 
Date:   2016-12-08T13:15:42Z

Fixed index consistency.

commit 1b6402fd2cc674f736319e84e50f769768b89a27
Author: EdShangGG 
Date:   2016-12-08T13:49:50Z

GG-11688 Extend Backup SPI to get information about backup from whole 
cluster
-new tests
-new checks 

Re: IGNITE-602

[Vladimir Ozerov]

Yes, my idea was around it - we need to stop recursion somehow. On the
other hand, position-based format is not very user-friendly, apparently.
May be some other approaches will be more suitable, but I cannot think of
anything else.

On Thu, Feb 16, 2017 at 2:26 PM, Дмитрий Рябов 
wrote:

> Hello, Vladimir. Do you mean something like "ArrayList [size=1,
> name=ArrayList [size=1, ArrayList {position 0}]]"?
>
> 2017-02-16 12:32 GMT+03:00 Vladimir Ozerov :
>
> > Hi Dmitriy,
> >
> > We should print all objects, because this is the whole purpose of
> > GridToStringBuilder class - to print as much as possible in pretty
> format.
> > For cyclic references, we should introduce smarter approach, ensuring
> that
> > certain object is printed only once, I would use a kind of stack or
> > IdentityHashMap to track already printed entries and then print a
> reference
> > to them instead of the whole body.
> >
> > We use similar approach for binary objects, see
> > BinaryObjectExImpl.toString(...)
> > method. In this case (hash + body) is printed normally, but when a cycle
> is
> > found, we print only (hash). This is not very suitable for
> > GridToStringBuilder, as we definitely do not want output to be flooded
> with
> > hashes, which are useless in common case. May be it makes sense to
> object's
> > position in already printed string.
> >
> > Vladimir.
> >
> >
> > On Wed, Feb 15, 2017 at 3:07 PM, Дмитрий Рябов 
> > wrote:
> >
> > > Hello, can you answer me a simple question?
> > >
> > > We have 2 looping lists:
> > >
> > > ArrayList list1 = new ArrayList<>();
> > > ArrayList list2 = new ArrayList<>();
> > >
> > > list2.add(list1);
> > > list1.add(list2);
> > >
> > > Class GridToStringBuilder represent them into string.
> > >
> > > Simple public static  String toString(Class cls, T obj) method
> > > returns string "ArrayList [size=1]" for each list.
> > >
> > > *Question is* how should look the result of toString(Class cls, T
> obj,
> > > String name, @Nullable Object val) method and other methods with
> > additional
> > > values?
> > > "ArrayList [size=1, name=ArrayList[size=1]]" or something else?
> > >
> > > The trouble is in GridStringBuilder.a(Object obj) method - it tries to
> > > append collection's toString() method which invokes toString() on every
> > > element.
> > >
> >
>

Re: Apache Ignite 1.9

[Anton Vinogradov]

Igniters,

We're planning to have a code freeze tomorrow, Feb 17 19.00 MSK.
Here's the list of issues we especially expect to be done in 1.9:

IGNITE-4106 SQL: parallelize sql queries over cache local partitions Andrew
Mashenkov
IGNITE-4670 CPP: Implement LoadCache method Task Igor Sapego
IGNITE-3860 Improve 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 Spark 2.0 Evgenii Zhuravlev
IGNITE-1794 Ignite should support Hibernate 5 Mykola Pereyma
IGNITE-4523 Allow distributed SQL query execution over explicit set of
partitions Alexei Scherbakov

Guys, please confirm that you will be able to complete listed tasks till
Feb 17 19.00 MSK.

On Thu, Feb 16, 2017 at 2:31 PM, Anton Vinogradov 
wrote:

> Denis,
>
> Evgenii Zhuravlev going to fix this issue. I'll provide him help if
> necessarry.
>
> On Wed, Feb 15, 2017 at 8:03 PM, Denis Magda  wrote:
>
>> Anton,
>>
>> The implementation is correct and was reviewed by Val long time ago. The
>> only issue that is left is the compilation in *TeamCity* only.
>> You fixed it for one scala version and now should simply do the same for
>> other scala version by adding a new suite to TeamCity and adjusting the pom.
>>
>> —
>> Denis
>>
>> > On Feb 15, 2017, at 1:20 AM, Anton Vinogradov 
>> wrote:
>> >
>> > Denis,
>> >
>> > I don't know what is the plan for this issue.
>> > You asked me to fix compilation and thats what I done :) , but I'm not
>> sure
>> > that issue implemented in proper way. I don't like changes I've done,
>> they
>> > looks redundant although it works.
>> > Do we have somebody more familiar with spark inside the community?
>> > We have to review what we already done and figure out what's left.
>> >
>> > On Wed, Feb 15, 2017 at 5:01 AM, Denis Magda  wrote:
>> >
>> >> Continuing Spark related topic...
>> >>
>> >> This ticket definitely must be included in 1.9:
>> >> https://issues.apache.org/jira/browse/IGNITE-3710 <
>> >> https://issues.apache.org/jira/browse/IGNITE-3710>
>> >>
>> >> We can’t longer afford torture Ignite Shared RDD users who have to use
>> an
>> >> outdated Spark version.
>> >>
>> >> Anton, could you finalize it this week? As far as I remember, the only
>> >> thing that is left is to add a missing test suite to Team City.
>> >>
>> >> —
>> >> Denis
>> >>
>> >>> On Feb 14, 2017, at 5:00 PM, Denis Magda  wrote:
>> >>>
>> >>> Reviewed and merged the first (!) Ignite Shared RDD examples
>> contributed
>> >> by Manish:
>> >>>
>> >>> https://issues.apache.org/jira/browse/IGNITE-4526
>> >>>
>> >>> Java:
>> >>> https://github.com/apache/ignite/blob/b461cb47882861356ede58775bd9e2
>> >> 53dcf26202/examples/src/main/java8/org/apache/ignite/example
>> s/java8/spark/
>> >> SharedRDDExample.java
>> >>>
>> >>> Scala:
>> >>> https://github.com/apache/ignite/blob/b461cb47882861356ede58775bd9e2
>> >> 53dcf26202/examples/src/main/scala/org/apache/ignite/
>> >> scalar/examples/spark/ScalarSharedRDDExample.scala
>> >>>
>> >>> Manish, thanks for making the life of Apache Ignite users easier. No
>> >> they can refer to your examples while learning Ignite Shared RDD API.
>> >>>
>> >>> —
>> >>> Denis
>> >>>
>>  On Feb 14, 2017, at 1:21 AM, Anton Vinogradov <
>> avinogra...@gridgain.com>
>> >> wrote:
>> 
>> >
>> > Can we push to 1.9 and then merge/rebase to master?
>> 
>> 
>>  Yes, that's *correct *too, but only *megre *should be used.
>> 
>>  On Tue, Feb 14, 2017 at 12:19 PM, Vladimir Ozerov <
>> voze...@gridgain.com
>> >>>
>>  wrote:
>> 
>> > Can we push to 1.9 and then merge/rebase to master? It should be
>> more
>> > reliable than cherry-picking.
>> >
>> > On Tue, Feb 14, 2017 at 12:15 PM, Anton Vinogradov <
>> > avinogra...@gridgain.com
>> >> wrote:
>> >
>> >> Denis,
>> >>
>> >> Merge to the master first and then cherry-pick to 1.9 from there
>> is a
>> >> *correct
>> >> *case.
>> >>
>> >> On Tue, Feb 14, 2017 at 5:24 AM, Dmitriy Setrakyan <
>> > dsetrak...@apache.org>
>> >> wrote:
>> >>
>> >>> Thanks, Denis!
>> >>>
>> >>> On Mon, Feb 13, 2017 at 5:49 PM, Denis Magda 
>> > wrote:
>> >>>
>>  Well, merged Kubernetes integration to the master and
>> cherry-picked
>> > to
>>  1.9. The docs and getting started for readme.io to be done soon.
>> 
>>  —
>>  Denis
>> 
>> > On Feb 13, 2017, at 9:10 AM, Denis Magda 
>> > wrote:
>> >
>> > Do I merge to the master first and then cherry-pick to 1.9 from
>> >> there?
>> >
>> > —
>> > Denis
>> >
>> >> On Feb 13, 2017, at 8:21 AM, Anton Vinogradov <
>> >>> avinogra...@gridgain.com>
>>  wrote:
>> >>
>> >> Igniters,
>> 

IGNITE-2626 is cloned?

[ALEKSEY KUZNETSOV]

Hi! about https://issues.apache.org/jira/browse/IGNITE-2626. Im sure this
ticket is cloned from https://issues.apache.org/jira/browse/IGNITE-3191,
because it was implemented there. And im confused with code status : fields
order is somehow deprecated. This ticket -
https://issues.apache.org/jira/browse/IGNITE-4695 must have covered fields
order.
-- 

*Best Regards,*

*Kuznetsov Aleksey*

DML usability: routing single column to several object fields

[Vladimir Ozerov]

Igniters,

Consider the following pattern which is typically used by users when
working through cache API and quering data through SQL at the same time:

class Person {
@QuerySqlField
long id;

@QuerySqlField
String name;
}

cache.put(*id*, new Person(*id*, name));

SELECT *id*, name FROM person;

Notice that ID is stored twice per cache record - once for key, and once
for value. This pattern is very convenient for users - loose some little
space due to duplication on the one hand, but have self-contained value
with all necessary data on the other. In fact virtually all production
systems I saw followed this approach and had some minor duplication.

It seems this approach doesn't work well with DML and upcoming DDL. When
executing INSERT INTO Person VALUES (:id, :name), I specify two attributes
which must update three cache fields.

In order to preserve usability of native cache API when DML is involved, we
need ability to map certain attribute to several Object properties.
Probably this can be achieved with additional field property which defines
that it belongs to a group mapped to an attribute. May be existing aliases
could be used for this.

Or we can ignore the problem sacrificing cache API usability a bit in case
of DML/DDL

Any ideas on whether we need it, and how to design public API?

Vladimir.

[GitHub] ignite pull request #1543: IGNITE-4628 Add Java callback support for platfor...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/1543

IGNITE-4628 Add Java callback support for platform plugins



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4628

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1543.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1543


commit 17009187cb4ae14bfc33c9b04160b3fe729b5435
Author: Pavel Tupitsyn 
Date:   2017-02-16T12:43:12Z

IGNITE-4628 Add Java callback support for platform plugins




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1542: IGNITE-4710 extended optimistic tx lock conflict ...

[zstan]

Github user zstan closed the pull request at:

https://github.com/apache/ignite/pull/1542


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: general question

[Andrey Mashenkov]

Hi Alexey,

See how
org.apache.ignite.internal.processors.cache.CacheEvictableEntryImpl.meta()
is used by,
e.g. org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicy.touch()
method that is calling when entry accessed.



On Wed, Feb 15, 2017 at 6:10 PM, ALEKSEY KUZNETSOV  wrote:

> hmm, why and how EvictionManager tracks an entry ?
>
> вт, 14 февр. 2017 г. в 23:07, Andrey Mashenkov  >:
>
> > Hi Aleksey,
> >
> > EvictableEntry.meta is used by EvictionManager to track entry.
> > Actually it may contains Node of EvictionPolicy queue to manupulate queue
> > items in more efficient way.
> >
> > On Tue, Feb 14, 2017 at 4:26 PM, ALEKSEY KUZNETSOV <
> > alkuznetsov...@gmail.com
> > > wrote:
> >
> > > need help. What is the use of EvictableEntry.meta  ? Why do we need to
> > ship
> > > some meta to entry ?
> > > --
> > >
> > > *Best Regards,*
> > >
> > > *Kuznetsov Aleksey*
> > >
> >
> >
> >
> > --
> > Best regards,
> > Andrey V. Mashenkov
> >
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>



-- 
Best regards,
Andrey V. Mashenkov

[GitHub] ignite pull request #1500: ignite-3477-idx2

[kdudkov]

Github user kdudkov closed the pull request at:

https://github.com/apache/ignite/pull/1500


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1544: IGNITE-4710: extended optimistic tx lock conflict...

[zstan]

GitHub user zstan opened a pull request:

https://github.com/apache/ignite/pull/1544

IGNITE-4710: extended optimistic tx lock conflict exception message



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4710

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1544.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1544


commit a0bfcb18d4deaa3b7fabc33b186f472a34e8709f
Author: Evgeny Stanilovskiy 
Date:   2017-02-16T12:59:03Z

IGNITE-4710: extended optimistic tx lock conflict exception message




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-4711) Propagate platform cache plugin configuration to Java

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4711:
--

 Summary: Propagate platform cache plugin configuration to Java
 Key: IGNITE-4711
 URL: https://issues.apache.org/jira/browse/IGNITE-4711
 Project: Ignite
  Issue Type: Sub-task
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.0


Same as IGNITE-4685 but for cache plugins.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1545: IGNITE-2552 EvictionPolicies refactored, logic ch...

[voipp]

GitHub user voipp opened a pull request:

https://github.com/apache/ignite/pull/1545

IGNITE-2552 EvictionPolicies refactored, logic changed

tests are in subclasses of EvictionAbstractTest

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/voipp/ignite IGNITE-2552

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1545.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1545


commit 651deeb058854e25b74368508ead4def31a016dc
Author: voipp 
Date:   2017-02-15T08:54:48Z

IGNITE-2552 EvictionPolicies refactored, logic changed




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Apache Ignite 1.9

[Alexander Paschenko]

Hi,

There are some questions regarding IGNITE-4169 - probably some design
approval will be required from Dmitry S. However, chances are good
that we'll make it in time.

- Alex

2017-02-16 14:48 GMT+03:00 Anton Vinogradov :
> Igniters,
>
> We're planning to have a code freeze tomorrow, Feb 17 19.00 MSK.
> Here's the list of issues we especially expect to be done in 1.9:
>
> IGNITE-4106 SQL: parallelize sql queries over cache local partitions Andrew
> Mashenkov
> IGNITE-4670 CPP: Implement LoadCache method Task Igor Sapego
> IGNITE-3860 Improve 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 Spark 2.0 Evgenii Zhuravlev
> IGNITE-1794 Ignite should support Hibernate 5 Mykola Pereyma
> IGNITE-4523 Allow distributed SQL query execution over explicit set of
> partitions Alexei Scherbakov
>
> Guys, please confirm that you will be able to complete listed tasks till
> Feb 17 19.00 MSK.
>
> On Thu, Feb 16, 2017 at 2:31 PM, Anton Vinogradov 
> wrote:
>
>> Denis,
>>
>> Evgenii Zhuravlev going to fix this issue. I'll provide him help if
>> necessarry.
>>
>> On Wed, Feb 15, 2017 at 8:03 PM, Denis Magda  wrote:
>>
>>> Anton,
>>>
>>> The implementation is correct and was reviewed by Val long time ago. The
>>> only issue that is left is the compilation in *TeamCity* only.
>>> You fixed it for one scala version and now should simply do the same for
>>> other scala version by adding a new suite to TeamCity and adjusting the pom.
>>>
>>> —
>>> Denis
>>>
>>> > On Feb 15, 2017, at 1:20 AM, Anton Vinogradov 
>>> wrote:
>>> >
>>> > Denis,
>>> >
>>> > I don't know what is the plan for this issue.
>>> > You asked me to fix compilation and thats what I done :) , but I'm not
>>> sure
>>> > that issue implemented in proper way. I don't like changes I've done,
>>> they
>>> > looks redundant although it works.
>>> > Do we have somebody more familiar with spark inside the community?
>>> > We have to review what we already done and figure out what's left.
>>> >
>>> > On Wed, Feb 15, 2017 at 5:01 AM, Denis Magda  wrote:
>>> >
>>> >> Continuing Spark related topic...
>>> >>
>>> >> This ticket definitely must be included in 1.9:
>>> >> https://issues.apache.org/jira/browse/IGNITE-3710 <
>>> >> https://issues.apache.org/jira/browse/IGNITE-3710>
>>> >>
>>> >> We can’t longer afford torture Ignite Shared RDD users who have to use
>>> an
>>> >> outdated Spark version.
>>> >>
>>> >> Anton, could you finalize it this week? As far as I remember, the only
>>> >> thing that is left is to add a missing test suite to Team City.
>>> >>
>>> >> —
>>> >> Denis
>>> >>
>>> >>> On Feb 14, 2017, at 5:00 PM, Denis Magda  wrote:
>>> >>>
>>> >>> Reviewed and merged the first (!) Ignite Shared RDD examples
>>> contributed
>>> >> by Manish:
>>> >>>
>>> >>> https://issues.apache.org/jira/browse/IGNITE-4526
>>> >>>
>>> >>> Java:
>>> >>> https://github.com/apache/ignite/blob/b461cb47882861356ede58775bd9e2
>>> >> 53dcf26202/examples/src/main/java8/org/apache/ignite/example
>>> s/java8/spark/
>>> >> SharedRDDExample.java
>>> >>>
>>> >>> Scala:
>>> >>> https://github.com/apache/ignite/blob/b461cb47882861356ede58775bd9e2
>>> >> 53dcf26202/examples/src/main/scala/org/apache/ignite/
>>> >> scalar/examples/spark/ScalarSharedRDDExample.scala
>>> >>>
>>> >>> Manish, thanks for making the life of Apache Ignite users easier. No
>>> >> they can refer to your examples while learning Ignite Shared RDD API.
>>> >>>
>>> >>> —
>>> >>> Denis
>>> >>>
>>>  On Feb 14, 2017, at 1:21 AM, Anton Vinogradov <
>>> avinogra...@gridgain.com>
>>> >> wrote:
>>> 
>>> >
>>> > Can we push to 1.9 and then merge/rebase to master?
>>> 
>>> 
>>>  Yes, that's *correct *too, but only *megre *should be used.
>>> 
>>>  On Tue, Feb 14, 2017 at 12:19 PM, Vladimir Ozerov <
>>> voze...@gridgain.com
>>> >>>
>>>  wrote:
>>> 
>>> > Can we push to 1.9 and then merge/rebase to master? It should be
>>> more
>>> > reliable than cherry-picking.
>>> >
>>> > On Tue, Feb 14, 2017 at 12:15 PM, Anton Vinogradov <
>>> > avinogra...@gridgain.com
>>> >> wrote:
>>> >
>>> >> Denis,
>>> >>
>>> >> Merge to the master first and then cherry-pick to 1.9 from there
>>> is a
>>> >> *correct
>>> >> *case.
>>> >>
>>> >> On Tue, Feb 14, 2017 at 5:24 AM, Dmitriy Setrakyan <
>>> > dsetrak...@apache.org>
>>> >> wrote:
>>> >>
>>> >>> Thanks, Denis!
>>> >>>
>>> >>> On Mon, Feb 13, 2017 at 5:49 PM, Denis Magda 
>>> > wrote:
>>> >>>
>>>  Well, merged Kubernetes integration to the master and
>>> cherry-picked
>>> > to
>>>  1.9. The docs and getting started for readme.io to be done soon.
>>> 
>>>  —
>>>  Denis
>>> 
>>> > On F

IGNITE-2779 BinaryMarshaller caches must be cleaned during client reconnect.

[ALEKSEY KUZNETSOV]

will take the ticket https://issues.apache.org/jira/browse/IGNITE-2779
-- 

*Best Regards,*

*Kuznetsov Aleksey*

[GitHub] ignite pull request #1546: Ignite 3710 Upgrade ignite-spark module to Spark ...

[ezhuravl]

GitHub user ezhuravl opened a pull request:

https://github.com/apache/ignite/pull/1546

Ignite 3710 Upgrade ignite-spark module to Spark 2.0



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-3710

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1546.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1546


commit 20d63f35dfd9eedf6e4d1a8a4d3c43713a58edec
Author: Denis Magda 
Date:   2016-12-11T05:35:23Z

IGNITE-3710: Upgrade ignite-spark module to Spark 2.0

commit 1382071e39dbda57922ffbca6a6d1375397f9713
Author: Denis Magda 
Date:   2016-12-11T06:22:18Z

IGNITE-3710: including spark parent

commit d674081b5e671b645e132a18c2229cb279d550bc
Author: Denis Magda 
Date:   2016-12-11T06:27:31Z

IGNITE-3710: revert latest changes

commit 24ae9e5f3bae3edf1f2597f7416b271f4a534381
Author: Anton Vinogradov 
Date:   2016-12-16T12:21:06Z

IGNITE-3710 Dependency fix.

commit aa7f631cc3ccb1b8653724b63bc382850539efa7
Author: Anton Vinogradov 
Date:   2016-12-16T12:51:13Z

IGNITE-3710 Dependency fix.

commit fe02969a68eb4ae82f4d6cf0fc7fc9687b548793
Author: Anton Vinogradov 
Date:   2016-12-16T12:55:27Z

IGNITE-3710 Dependency fix.

commit e0b444c51f7e892b0e153046960afd9a6c6a791c
Author: Anton Vinogradov 
Date:   2016-12-16T13:16:47Z

IGNITE-3710 Dependency fix.

commit 2f4ff70ba0a2553b54a707b147a1dbdd94bd17f0
Author: Anton Vinogradov 
Date:   2016-12-16T17:26:05Z

IGNITE-3710 Dependency fix

commit 2c562ac38d0c418f77f07866d1c54da1f7c8903b
Author: Anton Vinogradov 
Date:   2016-12-16T17:50:28Z

IGNITE-3710 Dependency fix

commit 1c9d17de62fc993c130f53f207a1fb2797fba3d3
Author: Anton Vinogradov 
Date:   2016-12-16T17:58:23Z

IGNITE-3710 Dependency fix

commit 892c5415cc3e61c458157ddb740ec3e611339303
Author: Anton Vinogradov 
Date:   2016-12-19T09:11:06Z

IGNITE-3710 Dependency fix

commit 7412f391cd32233ff7cd08184cbe681d079a317b
Author: Evgenii Zhuravlev 
Date:   2017-02-16T14:14:51Z

IGNITE-3710 update spark to 2.1.0 and fix dependencies for 2.10




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1547: IGNITE-4670: Added LoadCache and LocalLoadCache m...

[isapego]

GitHub user isapego opened a pull request:

https://github.com/apache/ignite/pull/1547

IGNITE-4670: Added LoadCache and LocalLoadCache methods



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4670

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1547.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1547


commit a1c71f2711bd1acd1ddfbb1293506b309d66acc6
Author: Igor Sapego 
Date:   2017-02-13T19:05:20Z

IGNITE-4670: Added test. Fix for other tests.

commit 170c5b5257c349d60d923574e79d9f42e7b78094
Author: Igor Sapego 
Date:   2017-02-13T19:19:16Z

IGNITE-4670: Added LoadCache method stub.

commit eb7c28bc0b9efc5ca7799e4dc1ff827d0efbae6b
Author: Igor Sapego 
Date:   2017-02-14T16:15:28Z

IGNITE-4670: Basic implementation.

commit 5f252df7a2930aef0ba66bdee1c82716a44f0381
Author: Igor Sapego 
Date:   2017-02-15T15:35:23Z

IGNITE-4670: Added test.

commit d1b80fdf6000c0c294ba628d8f631a1252b16fad
Author: Igor Sapego 
Date:   2017-02-15T15:38:05Z

IGNITE-4670: Test suit dead code clean up

commit ea8babaa463f3422ff09fde92ced1084d4123e11
Author: Igor Sapego 
Date:   2017-02-15T16:46:54Z

IGNITE-4670: Added test

commit 1777393ba53d6209f9d4aa50c3621316e5c685f5
Author: Igor Sapego 
Date:   2017-02-16T14:29:12Z

IGNITE-4670: Added LocalLoadCache Implementation




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Apache Ignite 1.9

[Igor Sapego]

Anton,

IGNITE-4670 is almost ready. I believe, there is nothing to worry about.

Best Regards,
Igor

On Thu, Feb 16, 2017 at 5:16 PM, Alexander Paschenko <
alexander.a.pasche...@gmail.com> wrote:

> Hi,
>
> There are some questions regarding IGNITE-4169 - probably some design
> approval will be required from Dmitry S. However, chances are good
> that we'll make it in time.
>
> - Alex
>
> 2017-02-16 14:48 GMT+03:00 Anton Vinogradov :
> > Igniters,
> >
> > We're planning to have a code freeze tomorrow, Feb 17 19.00 MSK.
> > Here's the list of issues we especially expect to be done in 1.9:
> >
> > IGNITE-4106 SQL: parallelize sql queries over cache local partitions
> Andrew
> > Mashenkov
> > IGNITE-4670 CPP: Implement LoadCache method Task Igor Sapego
> > IGNITE-3860 Improve 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 Spark 2.0 Evgenii Zhuravlev
> > IGNITE-1794 Ignite should support Hibernate 5 Mykola Pereyma
> > IGNITE-4523 Allow distributed SQL query execution over explicit set of
> > partitions Alexei Scherbakov
> >
> > Guys, please confirm that you will be able to complete listed tasks till
> > Feb 17 19.00 MSK.
> >
> > On Thu, Feb 16, 2017 at 2:31 PM, Anton Vinogradov <
> avinogra...@gridgain.com>
> > wrote:
> >
> >> Denis,
> >>
> >> Evgenii Zhuravlev going to fix this issue. I'll provide him help if
> >> necessarry.
> >>
> >> On Wed, Feb 15, 2017 at 8:03 PM, Denis Magda  wrote:
> >>
> >>> Anton,
> >>>
> >>> The implementation is correct and was reviewed by Val long time ago.
> The
> >>> only issue that is left is the compilation in *TeamCity* only.
> >>> You fixed it for one scala version and now should simply do the same
> for
> >>> other scala version by adding a new suite to TeamCity and adjusting
> the pom.
> >>>
> >>> —
> >>> Denis
> >>>
> >>> > On Feb 15, 2017, at 1:20 AM, Anton Vinogradov <
> avinogra...@gridgain.com>
> >>> wrote:
> >>> >
> >>> > Denis,
> >>> >
> >>> > I don't know what is the plan for this issue.
> >>> > You asked me to fix compilation and thats what I done :) , but I'm
> not
> >>> sure
> >>> > that issue implemented in proper way. I don't like changes I've done,
> >>> they
> >>> > looks redundant although it works.
> >>> > Do we have somebody more familiar with spark inside the community?
> >>> > We have to review what we already done and figure out what's left.
> >>> >
> >>> > On Wed, Feb 15, 2017 at 5:01 AM, Denis Magda 
> wrote:
> >>> >
> >>> >> Continuing Spark related topic...
> >>> >>
> >>> >> This ticket definitely must be included in 1.9:
> >>> >> https://issues.apache.org/jira/browse/IGNITE-3710 <
> >>> >> https://issues.apache.org/jira/browse/IGNITE-3710>
> >>> >>
> >>> >> We can’t longer afford torture Ignite Shared RDD users who have to
> use
> >>> an
> >>> >> outdated Spark version.
> >>> >>
> >>> >> Anton, could you finalize it this week? As far as I remember, the
> only
> >>> >> thing that is left is to add a missing test suite to Team City.
> >>> >>
> >>> >> —
> >>> >> Denis
> >>> >>
> >>> >>> On Feb 14, 2017, at 5:00 PM, Denis Magda 
> wrote:
> >>> >>>
> >>> >>> Reviewed and merged the first (!) Ignite Shared RDD examples
> >>> contributed
> >>> >> by Manish:
> >>> >>>
> >>> >>> https://issues.apache.org/jira/browse/IGNITE-4526
> >>> >>>
> >>> >>> Java:
> >>> >>> https://github.com/apache/ignite/blob/
> b461cb47882861356ede58775bd9e2
> >>> >> 53dcf26202/examples/src/main/java8/org/apache/ignite/example
> >>> s/java8/spark/
> >>> >> SharedRDDExample.java
> >>> >>>
> >>> >>> Scala:
> >>> >>> https://github.com/apache/ignite/blob/
> b461cb47882861356ede58775bd9e2
> >>> >> 53dcf26202/examples/src/main/scala/org/apache/ignite/
> >>> >> scalar/examples/spark/ScalarSharedRDDExample.scala
> >>> >>>
> >>> >>> Manish, thanks for making the life of Apache Ignite users easier.
> No
> >>> >> they can refer to your examples while learning Ignite Shared RDD
> API.
> >>> >>>
> >>> >>> —
> >>> >>> Denis
> >>> >>>
> >>>  On Feb 14, 2017, at 1:21 AM, Anton Vinogradov <
> >>> avinogra...@gridgain.com>
> >>> >> wrote:
> >>> 
> >>> >
> >>> > Can we push to 1.9 and then merge/rebase to master?
> >>> 
> >>> 
> >>>  Yes, that's *correct *too, but only *megre *should be used.
> >>> 
> >>>  On Tue, Feb 14, 2017 at 12:19 PM, Vladimir Ozerov <
> >>> voze...@gridgain.com
> >>> >>>
> >>>  wrote:
> >>> 
> >>> > Can we push to 1.9 and then merge/rebase to master? It should be
> >>> more
> >>> > reliable than cherry-picking.
> >>> >
> >>> > On Tue, Feb 14, 2017 at 12:15 PM, Anton Vinogradov <
> >>> > avinogra...@gridgain.com
> >>> >> wrote:
> >>> >
> >>> >> Denis,
> >>> >>
> >>> >> Merge to the master first and then cherry-pick to 1.9 from there
> >>> is a
> >>> 

[GitHub] ignite pull request #1543: IGNITE-4628 Add Java callback support for platfor...

[ptupitsyn]

Github user ptupitsyn closed the pull request at:

https://github.com/apache/ignite/pull/1543


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Apache Ignite 1.9

[Andrey Mashenkov]

Anton,

IGNITE-4106 is done.

On Thu, Feb 16, 2017 at 5:36 PM, Igor Sapego  wrote:

> Anton,
>
> IGNITE-4670 is almost ready. I believe, there is nothing to worry about.
>
> Best Regards,
> Igor
>
> On Thu, Feb 16, 2017 at 5:16 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
> > Hi,
> >
> > There are some questions regarding IGNITE-4169 - probably some design
> > approval will be required from Dmitry S. However, chances are good
> > that we'll make it in time.
> >
> > - Alex
> >
> > 2017-02-16 14:48 GMT+03:00 Anton Vinogradov :
> > > Igniters,
> > >
> > > We're planning to have a code freeze tomorrow, Feb 17 19.00 MSK.
> > > Here's the list of issues we especially expect to be done in 1.9:
> > >
> > > IGNITE-4106 SQL: parallelize sql queries over cache local partitions
> > Andrew
> > > Mashenkov
> > > IGNITE-4670 CPP: Implement LoadCache method Task Igor Sapego
> > > IGNITE-3860 Improve 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 Spark 2.0 Evgenii Zhuravlev
> > > IGNITE-1794 Ignite should support Hibernate 5 Mykola Pereyma
> > > IGNITE-4523 Allow distributed SQL query execution over explicit set of
> > > partitions Alexei Scherbakov
> > >
> > > Guys, please confirm that you will be able to complete listed tasks
> till
> > > Feb 17 19.00 MSK.
> > >
> > > On Thu, Feb 16, 2017 at 2:31 PM, Anton Vinogradov <
> > avinogra...@gridgain.com>
> > > wrote:
> > >
> > >> Denis,
> > >>
> > >> Evgenii Zhuravlev going to fix this issue. I'll provide him help if
> > >> necessarry.
> > >>
> > >> On Wed, Feb 15, 2017 at 8:03 PM, Denis Magda 
> wrote:
> > >>
> > >>> Anton,
> > >>>
> > >>> The implementation is correct and was reviewed by Val long time ago.
> > The
> > >>> only issue that is left is the compilation in *TeamCity* only.
> > >>> You fixed it for one scala version and now should simply do the same
> > for
> > >>> other scala version by adding a new suite to TeamCity and adjusting
> > the pom.
> > >>>
> > >>> —
> > >>> Denis
> > >>>
> > >>> > On Feb 15, 2017, at 1:20 AM, Anton Vinogradov <
> > avinogra...@gridgain.com>
> > >>> wrote:
> > >>> >
> > >>> > Denis,
> > >>> >
> > >>> > I don't know what is the plan for this issue.
> > >>> > You asked me to fix compilation and thats what I done :) , but I'm
> > not
> > >>> sure
> > >>> > that issue implemented in proper way. I don't like changes I've
> done,
> > >>> they
> > >>> > looks redundant although it works.
> > >>> > Do we have somebody more familiar with spark inside the community?
> > >>> > We have to review what we already done and figure out what's left.
> > >>> >
> > >>> > On Wed, Feb 15, 2017 at 5:01 AM, Denis Magda 
> > wrote:
> > >>> >
> > >>> >> Continuing Spark related topic...
> > >>> >>
> > >>> >> This ticket definitely must be included in 1.9:
> > >>> >> https://issues.apache.org/jira/browse/IGNITE-3710 <
> > >>> >> https://issues.apache.org/jira/browse/IGNITE-3710>
> > >>> >>
> > >>> >> We can’t longer afford torture Ignite Shared RDD users who have to
> > use
> > >>> an
> > >>> >> outdated Spark version.
> > >>> >>
> > >>> >> Anton, could you finalize it this week? As far as I remember, the
> > only
> > >>> >> thing that is left is to add a missing test suite to Team City.
> > >>> >>
> > >>> >> —
> > >>> >> Denis
> > >>> >>
> > >>> >>> On Feb 14, 2017, at 5:00 PM, Denis Magda 
> > wrote:
> > >>> >>>
> > >>> >>> Reviewed and merged the first (!) Ignite Shared RDD examples
> > >>> contributed
> > >>> >> by Manish:
> > >>> >>>
> > >>> >>> https://issues.apache.org/jira/browse/IGNITE-4526
> > >>> >>>
> > >>> >>> Java:
> > >>> >>> https://github.com/apache/ignite/blob/
> > b461cb47882861356ede58775bd9e2
> > >>> >> 53dcf26202/examples/src/main/java8/org/apache/ignite/example
> > >>> s/java8/spark/
> > >>> >> SharedRDDExample.java
> > >>> >>>
> > >>> >>> Scala:
> > >>> >>> https://github.com/apache/ignite/blob/
> > b461cb47882861356ede58775bd9e2
> > >>> >> 53dcf26202/examples/src/main/scala/org/apache/ignite/
> > >>> >> scalar/examples/spark/ScalarSharedRDDExample.scala
> > >>> >>>
> > >>> >>> Manish, thanks for making the life of Apache Ignite users easier.
> > No
> > >>> >> they can refer to your examples while learning Ignite Shared RDD
> > API.
> > >>> >>>
> > >>> >>> —
> > >>> >>> Denis
> > >>> >>>
> > >>>  On Feb 14, 2017, at 1:21 AM, Anton Vinogradov <
> > >>> avinogra...@gridgain.com>
> > >>> >> wrote:
> > >>> 
> > >>> >
> > >>> > Can we push to 1.9 and then merge/rebase to master?
> > >>> 
> > >>> 
> > >>>  Yes, that's *correct *too, but only *megre *should be used.
> > >>> 
> > >>>  On Tue, Feb 14, 2017 at 12:19 PM, Vladimir Ozerov <
> > >>> voze...@gridgain.com
> > >>> >>>
> > >>>  wrote:
> > >>> 
> > >>> > Can we pus

Re: Apache Ignite 1.9

[Andrey Mashenkov]

Anton,

 However, I would like Serj or somebody else take a look at IGNITE-4106.

On Thu, Feb 16, 2017 at 6:07 PM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Anton,
>
> IGNITE-4106 is done.
>
> On Thu, Feb 16, 2017 at 5:36 PM, Igor Sapego  wrote:
>
>> Anton,
>>
>> IGNITE-4670 is almost ready. I believe, there is nothing to worry about.
>>
>> Best Regards,
>> Igor
>>
>> On Thu, Feb 16, 2017 at 5:16 PM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>>
>> > Hi,
>> >
>> > There are some questions regarding IGNITE-4169 - probably some design
>> > approval will be required from Dmitry S. However, chances are good
>> > that we'll make it in time.
>> >
>> > - Alex
>> >
>> > 2017-02-16 14:48 GMT+03:00 Anton Vinogradov :
>> > > Igniters,
>> > >
>> > > We're planning to have a code freeze tomorrow, Feb 17 19.00 MSK.
>> > > Here's the list of issues we especially expect to be done in 1.9:
>> > >
>> > > IGNITE-4106 SQL: parallelize sql queries over cache local partitions
>> > Andrew
>> > > Mashenkov
>> > > IGNITE-4670 CPP: Implement LoadCache method Task Igor Sapego
>> > > IGNITE-3860 Improve 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 Spark 2.0 Evgenii Zhuravlev
>> > > IGNITE-1794 Ignite should support Hibernate 5 Mykola Pereyma
>> > > IGNITE-4523 Allow distributed SQL query execution over explicit set of
>> > > partitions Alexei Scherbakov
>> > >
>> > > Guys, please confirm that you will be able to complete listed tasks
>> till
>> > > Feb 17 19.00 MSK.
>> > >
>> > > On Thu, Feb 16, 2017 at 2:31 PM, Anton Vinogradov <
>> > avinogra...@gridgain.com>
>> > > wrote:
>> > >
>> > >> Denis,
>> > >>
>> > >> Evgenii Zhuravlev going to fix this issue. I'll provide him help if
>> > >> necessarry.
>> > >>
>> > >> On Wed, Feb 15, 2017 at 8:03 PM, Denis Magda 
>> wrote:
>> > >>
>> > >>> Anton,
>> > >>>
>> > >>> The implementation is correct and was reviewed by Val long time ago.
>> > The
>> > >>> only issue that is left is the compilation in *TeamCity* only.
>> > >>> You fixed it for one scala version and now should simply do the same
>> > for
>> > >>> other scala version by adding a new suite to TeamCity and adjusting
>> > the pom.
>> > >>>
>> > >>> —
>> > >>> Denis
>> > >>>
>> > >>> > On Feb 15, 2017, at 1:20 AM, Anton Vinogradov <
>> > avinogra...@gridgain.com>
>> > >>> wrote:
>> > >>> >
>> > >>> > Denis,
>> > >>> >
>> > >>> > I don't know what is the plan for this issue.
>> > >>> > You asked me to fix compilation and thats what I done :) , but I'm
>> > not
>> > >>> sure
>> > >>> > that issue implemented in proper way. I don't like changes I've
>> done,
>> > >>> they
>> > >>> > looks redundant although it works.
>> > >>> > Do we have somebody more familiar with spark inside the community?
>> > >>> > We have to review what we already done and figure out what's left.
>> > >>> >
>> > >>> > On Wed, Feb 15, 2017 at 5:01 AM, Denis Magda 
>> > wrote:
>> > >>> >
>> > >>> >> Continuing Spark related topic...
>> > >>> >>
>> > >>> >> This ticket definitely must be included in 1.9:
>> > >>> >> https://issues.apache.org/jira/browse/IGNITE-3710 <
>> > >>> >> https://issues.apache.org/jira/browse/IGNITE-3710>
>> > >>> >>
>> > >>> >> We can’t longer afford torture Ignite Shared RDD users who have
>> to
>> > use
>> > >>> an
>> > >>> >> outdated Spark version.
>> > >>> >>
>> > >>> >> Anton, could you finalize it this week? As far as I remember, the
>> > only
>> > >>> >> thing that is left is to add a missing test suite to Team City.
>> > >>> >>
>> > >>> >> —
>> > >>> >> Denis
>> > >>> >>
>> > >>> >>> On Feb 14, 2017, at 5:00 PM, Denis Magda 
>> > wrote:
>> > >>> >>>
>> > >>> >>> Reviewed and merged the first (!) Ignite Shared RDD examples
>> > >>> contributed
>> > >>> >> by Manish:
>> > >>> >>>
>> > >>> >>> https://issues.apache.org/jira/browse/IGNITE-4526
>> > >>> >>>
>> > >>> >>> Java:
>> > >>> >>> https://github.com/apache/ignite/blob/
>> > b461cb47882861356ede58775bd9e2
>> > >>> >> 53dcf26202/examples/src/main/java8/org/apache/ignite/example
>> > >>> s/java8/spark/
>> > >>> >> SharedRDDExample.java
>> > >>> >>>
>> > >>> >>> Scala:
>> > >>> >>> https://github.com/apache/ignite/blob/
>> > b461cb47882861356ede58775bd9e2
>> > >>> >> 53dcf26202/examples/src/main/scala/org/apache/ignite/
>> > >>> >> scalar/examples/spark/ScalarSharedRDDExample.scala
>> > >>> >>>
>> > >>> >>> Manish, thanks for making the life of Apache Ignite users
>> easier.
>> > No
>> > >>> >> they can refer to your examples while learning Ignite Shared RDD
>> > API.
>> > >>> >>>
>> > >>> >>> —
>> > >>> >>> Denis
>> > >>> >>>
>> > >>>  On Feb 14, 2017, at 1:21 AM, Anton Vinogradov <
>> > >>> avinogra...@gridgain.com>
>> > >>> >> wrote:
>> > >>> 
>> > >>> >
>> > >>> > C

[jira] [Created] (IGNITE-4712) Memory leaks in PageMemory

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-4712:


 Summary: Memory leaks in PageMemory
 Key: IGNITE-4712
 URL: https://issues.apache.org/jira/browse/IGNITE-4712
 Project: Ignite
  Issue Type: Bug
Reporter: Igor Seliverstov
 Fix For: 2.0


During performing put/get/remove operations on large objects (objects, which 
size is more than 1kb) allocated pages number constantly grows.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Implement IgniteZeromqStreamer to stream data from ZeroMQ

[Denis Magda]

Roman,

As the most experienced committer of the streaming components, could you do the 
review of Maxim’s changes?

—
Denis

> On Feb 16, 2017, at 1:23 AM, Kozlov Maxim  wrote:
> 
> Hello Igniters,
> 
> Please review and comment implementation ZeroMQ streamer.
> PR: https://github.com/apache/ignite/pull/1532 
> 
> Jira: https://issues.apache.org/jira/browse/IGNITE-533 
> 
> 
> 
> --
> Best Regards,
> Max K.
> 
> 
> 
> 

Re: ignite analysis with jepsen

[Denis Magda]

Evgeniy,

The price is high if you want Jepsen guys to do the testing of Ignite with 
their suites. We, as open source community, can’t afford it.

However, I didn’t know that the tests are open sourced. Is this something are 
ready to take over?

—
Denis

> On Feb 15, 2017, at 10:23 PM, Evgeniy Stanilovskiy  
> wrote:
> 
> Hello Igniters,
> 
> There is fresh doc about mongodb analysis with jepsen tool:
> https://jepsen.io/analyses/mongodb-3-4-0-rc3
> Looks like mongo soon would be production ready database )
> And what do you think about the same analysis for ignite?
> 
> I have no deal with jepsen but has a lot of positive feed backs.
> Spend a little time for introduction into
> https://github.com/jepsen-io/jepsen
> found all testing config under clojure language witch may cause some initial 
> troubles i think ..

Re: error - Failed to wait for partition release future

[Cameron Braid]

Hi,

Thanks for looking at my issue.

There are tags for 1.8.1, 1.8.2 and 1.8.3 at
https://github.com/gridgain/apache-ignite  so I have been trying using jars
built from those tags, including 1.9

I'm still getting the issues. What concerns me the most is that it is very
easy to lockup the whole grid.  I have tried various short (2s) .. long
(40s) FailureDetectionTimeout and I still get a lockup.  I've tried the
prefer ip4 as you suggested but it didn't make any difference.  I've
included my jvm args, an excerpt from the jvm gc logs, and some more recent
ignite logs.

Cheers

Cameron

*[jvm args]*

-Xms2G -Xmx2G

-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-XX:+PrintGCDateStamps
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10
-XX:GCLogFileSize=100M
-Xloggc:target/gc-log-devA.txt

-XX:+UseParNewGC  -XX:+UseConcMarkSweepGC  -XX:+UseTLAB
-XX:NewSize=128m  -XX:MaxNewSize=128m
-XX:MaxTenuringThreshold=0  -XX:SurvivorRatio=1024
-XX:+UseCMSInitiatingOccupancyOnly
-XX:CMSInitiatingOccupancyFraction=40 -XX:MaxGCPauseMillis=1000
-XX:InitiatingHeapOccupancyPercent=50  -XX:+UseCompressedOops
-XX:ParallelGCThreads=6  -XX:ConcGCThreads=6

*[GC logs]*

2017-02-17T02:43:31.345+1100: 1997.387: [CMS-concurrent-reset: 0.004/0.004
secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2017-02-17T02:43:32.099+1100: 1998.141: [GC (Allocation Failure)
2017-02-17T02:43:32.100+1100: 1998.141: [ParNew: 130485K->0K(131008K),
0.0332423 secs] 773911K->655291K(2097088K), 0.0336493 secs] [Times:
user=0.10 sys=0.00, real=0.04 secs]
2017-02-17T02:43:32.498+1100: 1998.539: [GC (Allocation Failure)
2017-02-17T02:43:32.498+1100: 1998.539: [ParNew: 130944K->0K(131008K),
0.0489761 secs] 786235K->683673K(2097088K), 0.0492079 secs] [Times:
user=0.13 sys=0.01, real=0.05 secs]
2017-02-17T02:43:33.578+1100: 1999.620: [GC (Allocation Failure)
2017-02-17T02:43:33.578+1100: 1999.620: [ParNew: 130944K->0K(131008K),
0.0589320 secs] 814617K->710468K(2097088K), 0.0594862 secs] [Times:
user=0.19 sys=0.01, real=0.06 secs]
2017-02-17T02:43:33.997+1100: 2000.038: [GC (Allocation Failure)
2017-02-17T02:43:33.997+1100: 2000.038: [ParNew: 130944K->0K(131008K),
0.0382098 secs] 841412K->723510K(2097088K), 0.0386616 secs] [Times:
user=0.11 sys=0.00, real=0.04 secs]
2017-02-17T02:43:34.724+1100: 2000.765: [GC (Allocation Failure)
2017-02-17T02:43:34.724+1100: 2000.765: [ParNew: 130944K->0K(131008K),
0.0061646 secs] 854454K->725669K(2097088K), 0.0064497 secs] [Times:
user=0.03 sys=0.01, real=0.01 secs]
2017-02-17T02:43:35.303+1100: 2001.344: [GC (Allocation Failure)
2017-02-17T02:43:35.303+1100: 2001.345: [ParNew: 130944K->0K(131008K),
0.0102684 secs] 856613K->727224K(2097088K), 0.0105370 secs] [Times:
user=0.04 sys=0.00, real=0.01 secs]
2017-02-17T02:43:35.582+1100: 2001.623: [GC (Allocation Failure)
2017-02-17T02:43:35.582+1100: 2001.623: [ParNew: 130944K->0K(131008K),
0.0201246 secs] 858168K->735764K(2097088K), 0.0204913 secs] [Times:
user=0.09 sys=0.00, real=0.02 secs]
2017-02-17T02:43:35.856+1100: 2001.898: [GC (Allocation Failure)
2017-02-17T02:43:35.856+1100: 2001.898: [ParNew: 130944K->0K(131008K),
0.0176264 secs] 866708K->745151K(2097088K), 0.0178741 secs] [Times:
user=0.08 sys=0.00, real=0.02 secs]
2017-02-17T02:43:36.554+1100: 2002.595: [GC (Allocation Failure)
2017-02-17T02:43:36.554+1100: 2002.596: [ParNew: 130944K->0K(131008K),
0.0480600 secs] 876095K->752482K(2097088K), 0.0483472 secs] [Times:
user=0.08 sys=0.00, real=0.05 secs]
2017-02-17T02:43:38.991+1100: 2005.033: [GC (Allocation Failure)
2017-02-17T02:43:38.991+1100: 2005.033: [ParNew: 130930K->0K(131008K),
0.0188153 secs] 883413K->764137K(2097088K), 0.0191396 secs] [Times:
user=0.08 sys=0.00, real=0.02 secs]
2017-02-17T02:43:40.428+1100: 2006.470: [GC (Allocation Failure)
2017-02-17T02:43:40.428+1100: 2006.470: [ParNew: 130941K->0K(131008K),
0.0272629 secs] 895079K->775860K(2097088K), 0.0274685 secs] [Times:
user=0.07 sys=0.01, real=0.02 secs]
2017-02-17T02:43:41.195+1100: 2007.237: [GC (Allocation Failure)
2017-02-17T02:43:41.195+1100: 2007.237: [ParNew: 130944K->0K(131008K),
0.0117222 secs] 906804K->778960K(2097088K), 0.0120822 secs] [Times:
user=0.05 sys=0.00, real=0.01 secs]
2017-02-17T02:43:41.919+1100: 2007.960: [GC (Allocation Failure)
2017-02-17T02:43:41.919+1100: 2007.961: [ParNew: 130944K->0K(131008K),
0.0181342 secs] 909904K->782162K(2097088K), 0.0183815 secs] [Times:
user=0.05 sys=0.00, real=0.02 secs]
2017-02-17T02:43:42.337+1100: 2008.378: [GC (Allocation Failure)
2017-02-17T02:43:42.337+1100: 2008.378: [ParNew: 130944K->0K(131008K),
0.0182636 secs] 913106K->790713K(2097088K), 0.0187463 secs] [Times:
user=0.08 sys=0.00, real=0.02 secs]
2017-02-17T02:43:42.358+1100: 2008.399: [GC (CMS Initial Mark) [1
CMS-initial-mark: 790713K(1966080K)] 791332K(2097088K), 0.0103648 secs]
[Times: user=0.02 sys=0.00, real=0.02 secs]
2017-02-17T02:43:42.368+1100: 2008.410: [CMS-concurrent-mark-start]
2017-02-17T02:43:42.668+1100: 2008.709: [CMS-concurrent-mark: 0.299/0.299
secs] [Times: user=1.76 sys=0.0

Re: error - Failed to wait for partition release future

[Andrey Mashenkov]

Hi Cameron,

You wrote on Apache Ignite Community dev-list.  Iginte does not have
versions like 1.8.x.
Git repository you refer to is not belong to the Apache Ignite project.


On Thu, Feb 16, 2017 at 6:58 PM, Cameron Braid  wrote:

> Hi,
>
> Thanks for looking at my issue.
>
> There are tags for 1.8.1, 1.8.2 and 1.8.3 at
> https://github.com/gridgain/apache-ignite  so I have been trying using
> jars
> built from those tags, including 1.9
>
> I'm still getting the issues. What concerns me the most is that it is very
> easy to lockup the whole grid.  I have tried various short (2s) .. long
> (40s) FailureDetectionTimeout and I still get a lockup.  I've tried the
> prefer ip4 as you suggested but it didn't make any difference.  I've
> included my jvm args, an excerpt from the jvm gc logs, and some more recent
> ignite logs.
>
> Cheers
>
> Cameron
>
> *[jvm args]*
>
> -Xms2G -Xmx2G
>
> -XX:+PrintGCDetails
> -XX:+PrintGCTimeStamps
> -XX:+PrintGCDateStamps
> -XX:+UseGCLogFileRotation
> -XX:NumberOfGCLogFiles=10
> -XX:GCLogFileSize=100M
> -Xloggc:target/gc-log-devA.txt
>
> -XX:+UseParNewGC  -XX:+UseConcMarkSweepGC  -XX:+UseTLAB
> -XX:NewSize=128m  -XX:MaxNewSize=128m
> -XX:MaxTenuringThreshold=0  -XX:SurvivorRatio=1024
> -XX:+UseCMSInitiatingOccupancyOnly
> -XX:CMSInitiatingOccupancyFraction=40 -XX:MaxGCPauseMillis=1000
> -XX:InitiatingHeapOccupancyPercent=50  -XX:+UseCompressedOops
> -XX:ParallelGCThreads=6  -XX:ConcGCThreads=6
>
> *[GC logs]*
>
> 2017-02-17T02:43:31.345+1100: 1997.387: [CMS-concurrent-reset: 0.004/0.004
> secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
> 2017-02-17T02:43:32.099+1100: 1998.141: [GC (Allocation Failure)
> 2017-02-17T02:43:32.100+1100: 1998.141: [ParNew: 130485K->0K(131008K),
> 0.0332423 secs] 773911K->655291K(2097088K), 0.0336493 secs] [Times:
> user=0.10 sys=0.00, real=0.04 secs]
> 2017-02-17T02:43:32.498+1100: 1998.539: [GC (Allocation Failure)
> 2017-02-17T02:43:32.498+1100: 1998.539: [ParNew: 130944K->0K(131008K),
> 0.0489761 secs] 786235K->683673K(2097088K), 0.0492079 secs] [Times:
> user=0.13 sys=0.01, real=0.05 secs]
> 2017-02-17T02:43:33.578+1100: 1999.620: [GC (Allocation Failure)
> 2017-02-17T02:43:33.578+1100: 1999.620: [ParNew: 130944K->0K(131008K),
> 0.0589320 secs] 814617K->710468K(2097088K), 0.0594862 secs] [Times:
> user=0.19 sys=0.01, real=0.06 secs]
> 2017-02-17T02:43:33.997+1100: 2000.038: [GC (Allocation Failure)
> 2017-02-17T02:43:33.997+1100: 2000.038: [ParNew: 130944K->0K(131008K),
> 0.0382098 secs] 841412K->723510K(2097088K), 0.0386616 secs] [Times:
> user=0.11 sys=0.00, real=0.04 secs]
> 2017-02-17T02:43:34.724+1100: 2000.765: [GC (Allocation Failure)
> 2017-02-17T02:43:34.724+1100: 2000.765: [ParNew: 130944K->0K(131008K),
> 0.0061646 secs] 854454K->725669K(2097088K), 0.0064497 secs] [Times:
> user=0.03 sys=0.01, real=0.01 secs]
> 2017-02-17T02:43:35.303+1100: 2001.344: [GC (Allocation Failure)
> 2017-02-17T02:43:35.303+1100: 2001.345: [ParNew: 130944K->0K(131008K),
> 0.0102684 secs] 856613K->727224K(2097088K), 0.0105370 secs] [Times:
> user=0.04 sys=0.00, real=0.01 secs]
> 2017-02-17T02:43:35.582+1100: 2001.623: [GC (Allocation Failure)
> 2017-02-17T02:43:35.582+1100: 2001.623: [ParNew: 130944K->0K(131008K),
> 0.0201246 secs] 858168K->735764K(2097088K), 0.0204913 secs] [Times:
> user=0.09 sys=0.00, real=0.02 secs]
> 2017-02-17T02:43:35.856+1100: 2001.898: [GC (Allocation Failure)
> 2017-02-17T02:43:35.856+1100: 2001.898: [ParNew: 130944K->0K(131008K),
> 0.0176264 secs] 866708K->745151K(2097088K), 0.0178741 secs] [Times:
> user=0.08 sys=0.00, real=0.02 secs]
> 2017-02-17T02:43:36.554+1100: 2002.595: [GC (Allocation Failure)
> 2017-02-17T02:43:36.554+1100: 2002.596: [ParNew: 130944K->0K(131008K),
> 0.0480600 secs] 876095K->752482K(2097088K), 0.0483472 secs] [Times:
> user=0.08 sys=0.00, real=0.05 secs]
> 2017-02-17T02:43:38.991+1100: 2005.033: [GC (Allocation Failure)
> 2017-02-17T02:43:38.991+1100: 2005.033: [ParNew: 130930K->0K(131008K),
> 0.0188153 secs] 883413K->764137K(2097088K), 0.0191396 secs] [Times:
> user=0.08 sys=0.00, real=0.02 secs]
> 2017-02-17T02:43:40.428+1100: 2006.470: [GC (Allocation Failure)
> 2017-02-17T02:43:40.428+1100: 2006.470: [ParNew: 130941K->0K(131008K),
> 0.0272629 secs] 895079K->775860K(2097088K), 0.0274685 secs] [Times:
> user=0.07 sys=0.01, real=0.02 secs]
> 2017-02-17T02:43:41.195+1100: 2007.237: [GC (Allocation Failure)
> 2017-02-17T02:43:41.195+1100: 2007.237: [ParNew: 130944K->0K(131008K),
> 0.0117222 secs] 906804K->778960K(2097088K), 0.0120822 secs] [Times:
> user=0.05 sys=0.00, real=0.01 secs]
> 2017-02-17T02:43:41.919+1100: 2007.960: [GC (Allocation Failure)
> 2017-02-17T02:43:41.919+1100: 2007.961: [ParNew: 130944K->0K(131008K),
> 0.0181342 secs] 909904K->782162K(2097088K), 0.0183815 secs] [Times:
> user=0.05 sys=0.00, real=0.02 secs]
> 2017-02-17T02:43:42.337+1100: 2008.378: [GC (Allocation Failure)
> 2017-02-17T02:43:42.337+1100: 2008.378: [ParNew: 130944K->0K(131008K),
> 0.0182636 secs] 913106K->790713K(209708

[jira] [Created] (IGNITE-4713) refactoring of GridFinishedFuture and GridFutureAdapter

[Alexander Menshikov (JIRA)]

Alexander Menshikov created IGNITE-4713:
---

 Summary:  refactoring of GridFinishedFuture and GridFutureAdapter
 Key: IGNITE-4713
 URL: https://issues.apache.org/jira/browse/IGNITE-4713
 Project: Ignite
  Issue Type: Improvement
  Components: community
Reporter: Alexander Menshikov
Assignee: Alexander Menshikov
Priority: Trivial


I propose to do refactoring of classes "GridFinishedFuture" and 
"GridFutureAdapter". These is field "resFlag" wiche can equals "ERR = 1" or 
"RES = 2". So I can replace it to one "bool haveResult" filed.

If there are no objections, I'm ready to proceed. If you find more such 
classes, please write about them.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

IGNITE-4713 : refactoring of GridFinishedFuture and GridFutureAdapter

[Александр Меньшиков]

Hello.

I propose to do refactoring of classes "GridFinishedFuture" and
"GridFutureAdapter". There is field "resFlag" which can equals "ERR = 1" or
"RES = 2". So I can replace it to one "bool haveResult" field.

If there are no objections, I'm ready to proceed. If you find more such
classes, please write about them.

[GitHub] ignite pull request #1548: IGNITE-4611

[daradurvs]

GitHub user daradurvs opened a pull request:

https://github.com/apache/ignite/pull/1548

IGNITE-4611



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/daradurvs/ignite ignite-4611

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1548.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1548


commit f1a8333665c6839c84d80a4862d5c441a6d00945
Author: daradurvs 
Date:   2017-02-16T16:22:29Z

ignite-4611: IgniteUuid implementer Binarylizable interface

commit 8fa4707079044de35d4c7f95e3a12d95082c238f
Author: daradurvs 
Date:   2017-02-16T16:47:41Z

ignite-4611: Refactoring

commit 57113eec8d26e9c4b44b4664889792691c7c2e18
Author: daradurvs 
Date:   2017-02-16T16:56:56Z

ignite-4611: truncated the code




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1515: IGNITE-4158

[daradurvs]

Github user daradurvs closed the pull request at:

https://github.com/apache/ignite/pull/1515


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

cache metadata progapagation

[Dmitriy Setrakyan]

Igniters,

I believe that we are not propagating cache metadata correctly, but I want
to confirm it with the community first.

Currently, it is possible in Ignite to split the cluster into logical
groups, and deploy caches only on certain nodes using NodeFilters. For
example, CacheA will reside only on Nodes 1, 2, and 3, and CacheB will
reside only on nodes 4 and 5. However, even in this case, it looks like the
cache metadata for both caches will be deployed on all the nodes.

It looks like the correct approach would be to honor the NodeFilter for a
 cache whenever deploying the cache metadata. Is there a reason for the
metadata to be deployed on all the nodes?

D.

Re: DML usability: routing single column to several object fields

[Dmitriy Setrakyan]

Vladimir,

When a table is created, user should specify the "primary key". We can
extract this field and use it as the key into the BTree index. This way it
will fit into the current design. Am I wrong?

D.

On Thu, Feb 16, 2017 at 4:33 AM, Vladimir Ozerov 
wrote:

> Igniters,
>
> Consider the following pattern which is typically used by users when
> working through cache API and quering data through SQL at the same time:
>
> class Person {
> @QuerySqlField
> long id;
>
> @QuerySqlField
> String name;
> }
>
> cache.put(*id*, new Person(*id*, name));
>
> SELECT *id*, name FROM person;
>
> Notice that ID is stored twice per cache record - once for key, and once
> for value. This pattern is very convenient for users - loose some little
> space due to duplication on the one hand, but have self-contained value
> with all necessary data on the other. In fact virtually all production
> systems I saw followed this approach and had some minor duplication.
>
> It seems this approach doesn't work well with DML and upcoming DDL. When
> executing INSERT INTO Person VALUES (:id, :name), I specify two attributes
> which must update three cache fields.
>
> In order to preserve usability of native cache API when DML is involved, we
> need ability to map certain attribute to several Object properties.
> Probably this can be achieved with additional field property which defines
> that it belongs to a group mapped to an attribute. May be existing aliases
> could be used for this.
>
> Or we can ignore the problem sacrificing cache API usability a bit in case
> of DML/DDL
>
> Any ideas on whether we need it, and how to design public API?
>
> Vladimir.
>

Re: DML data streaming

[Dmitriy Setrakyan]

Vladimir, I am not sure I understand your point. The value type name should
be the table name, no?

On Thu, Feb 16, 2017 at 12:13 AM, Vladimir Ozerov 
wrote:

> Dima,
>
> At this point we require the following additional data which is outside of
> standard SQL:
> - Key type
> - Value type
> - Set of key columns
>
> I do not know yet how we will define these values. At the very least we can
> calculate them automatically in some cases. For "keyFieldName" and
> "valFieldName" things are easier, as we can always derive them from table
> definition.
>
> Example 1 - primitives:
>
> CREATE TABLE (
> *pk_id* BIGINT PRIMARY KEY,
> *val*   BIGINT
> )
>
> keyFieldName = "*pk_id*", valFieldName = "*val*"
>
> Example 2 - composites:
>
> CREATE TABLE (
> *pk_id* BIGINT PRIMARY KEY,
> val1  BIGINT,
> val2  VARCHAR
> )
>
> keyFieldName = "*pk_id*", valFieldName = null (because value is complex and
> is composed of two attributes).
>
> Vladimir.
>
>
> On Wed, Feb 15, 2017 at 11:42 PM, Dmitriy Setrakyan  >
> wrote:
>
> > On Wed, Feb 15, 2017 at 4:28 AM, Vladimir Ozerov 
> > wrote:
> >
> > > Ok, let's put aside current fields configuration, I'll create separate
> > > thread for it. As far as _KEY and _VAL, proposed change is exactly
> about
> > > mappings:
> > >
> > > class QueryEntity {
> > > ...
> > > String keyFieldName;
> > > String valFieldName;
> > > ...
> > > }
> > >
> > > The key thing is that we will not require users to be aware of our
> system
> > > columns. Normally user should not bother about existence of hidden _KEY
> > and
> > > _VAL columns. Instead, we just allow them to optionally reference the
> > whole
> > > key and/or val through predefined name.
> > >
> > >
> > Vladimir, how will it work from the DDL perspective. Let's say whenever
> > user wants to create a table in Ignite?
> >
>

Re: error - Failed to wait for partition release future

[Cameron Braid]

Ok,  I have moved to using apache ignite 1.8.0 jar and the same issue is
there.

I don't believe that  it is slow networking that is causing this as it does
also happen on a single host single node cluster - its hard to reproduce
but it does happen.

I've included a log from the grid locking up  on a single node grid.

Any ideas on what I can do to stop the cluster from locking up ?

Feb 17 09:09:22 webapp-97-3v11l webapp  85614 WARN
o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture
[exchange-worker-#26%webapp%] Failed to wait for partition release future
[topVer=AffinityTopologyVersion [topVer=1, minorTopVer=6],
node=68845172-67fb-4f49-ae81-f3024ef89e66]. Dumping pending objects that
might be the cause:
Feb 17 09:09:22 webapp-97-3v11l webapp  85614 WARN
o.a.i.i.p.c.GridCachePartitionExchangeManager [exchange-worker-#26%webapp%]
Ready affinity version: AffinityTopologyVersion [topVer=1, minorTopVer=5]
Feb 17 09:09:22 webapp-97-3v11l webapp  85619 WARN
o.a.i.i.p.c.GridCachePartitionExchangeManager [exchange-worker-#26%webapp%]
Last exchange future: GridDhtPartitionsExchangeFuture [dummy=false,
forcePreload=false, reassign=false, discoEvt=DiscoveryCustomEvent
[customMsg=DynamicCacheChangeBatch [reqs=[DynamicCacheChangeRequest
[deploymentId=d7f09f84a51-923f7cb7-d9c2-46e8-b121-c7fe21e14aa2,
startCfg=CacheConfiguration [name=query.starRatings.aggregate,
storeConcurrentLoadAllThreshold=5, rebalancePoolSize=2,
rebalanceTimeout=1, evictPlc=LruEvictionPolicy [max=500, batchSize=1,
maxMemSize=0, memSize=0, size=0], evictSync=false, evictKeyBufSize=1024,
evictSyncConcurrencyLvl=4, evictSyncTimeout=1, evictFilter=null,
evictMaxOverflowRatio=10.0, eagerTtl=true, dfltLockTimeout=0,
startSize=150, nearCfg=null, writeSync=PRIMARY_SYNC, storeFactory=null,
storeKeepBinary=false, loadPrevVal=false,
aff=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction@3cfe01ec,
cacheMode=REPLICATED, atomicityMode=ATOMIC, atomicWriteOrderMode=PRIMARY,
backups=2147483647, invalidate=false, tmLookupClsName=null,
rebalanceMode=ASYNC, rebalanceOrder=0, rebalanceBatchSize=524288,
rebalanceBatchesPrefetchCount=2, offHeapMaxMem=-1, swapEnabled=false,
maxConcurrentAsyncOps=500, writeBehindEnabled=false,
writeBehindFlushSize=10240, writeBehindFlushFreq=5000,
writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, maxQryIterCnt=1024,
memMode=ONHEAP_TIERED,
affMapper=o.a.i.i.processors.cache.CacheDefaultBinaryAffinityKeyMapper@387ac79,
rebalanceDelay=0, rebalanceThrottle=0, interceptor=null,
longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true,
nodeFilter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate@2a423797,
sqlSchema=null, sqlEscapeAll=false, sqlOnheapRowCacheSize=10240,
snapshotableIdx=false, cpOnRead=true, topValidator=null], cacheType=USER,
initiatingNodeId=68845172-67fb-4f49-ae81-f3024ef89e66, nearCacheCfg=null,
clientStartOnly=false, stop=false, close=false, failIfExists=true,
template=false, rcvdFrom=null, exchangeNeeded=true, cacheFutTopVer=null,
cacheName=query.starRatings.aggregate]], clientNodes=null,
id=e7f09f84a51-923f7cb7-d9c2-46e8-b121-c7fe21e14aa2,
clientReconnect=false], affTopVer=AffinityTopologyVersion [topVer=1,
minorTopVer=6], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
[id=68845172-67fb-4f49-ae81-f3024ef89e66, addrs=[0:0:0:0:0:0:0:1%lo,
10.129.1.132, 127.0.0.1], sockAddrs=[webapp-97-3v11l/10.129.1.132:47500,
/0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1487282891381, loc=true,
ver=1.8.1#20161208-sha1:a8fcb7b2, isClient=false], topVer=1,
nodeId8=68845172, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1487282952548]], crd=TcpDiscoveryNode
[id=68845172-67fb-4f49-ae81-f3024ef89e66, addrs=[0:0:0:0:0:0:0:1%lo,
10.129.1.132, 127.0.0.1], sockAddrs=[webapp-97-3v11l/10.129.1.132:47500,
/0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500], discPort=47500, order=1,
intOrder=1, lastExchangeTime=1487282891381, loc=true,
ver=1.8.1#20161208-sha1:a8fcb7b2, isClient=false],
exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion
[topVer=1, minorTopVer=6], nodeId=68845172, evt=DISCOVERY_CUSTOM_EVT],
added=true, initFut=GridFutureAdapter [resFlag=0, res=null,
startTime=1487282952548, endTime=0, ignoreInterrupts=false, state=INIT],
init=false, topSnapshot=null, lastVer=null,
partReleaseFut=GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=3,
done=false, cancelled=false, err=null, futs=[true, true, true, false]],
affChangeMsg=null, skipPreload=false, clientOnlyExchange=false,
initTs=1487282952548, centralizedAff=false, evtLatch=0, remaining=[],
srvNodes=[TcpDiscoveryNode [id=68845172-67fb-4f49-ae81-f3024ef89e66,
addrs=[0:0:0:0:0:0:0:1%lo, 10.129.1.132, 127.0.0.1],
sockAddrs=[webapp-97-3v11l/10.129.1.132:47500, /0:0:0:0:0:0:0:1%lo:47500, /
127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1487282891381, loc=true, ver=1.8.1#20161208-sha1:a8fcb7b2,
isClient=false]], super=GridFutureAdapter [resFlag=0, res=null,
startTime=14

[jira] [Created] (IGNITE-4714) Web console: Disable refresh rate for explain query

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-4714:
-

 Summary: Web console: Disable refresh rate for explain query
 Key: IGNITE-4714
 URL: https://issues.apache.org/jira/browse/IGNITE-4714
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Affects Versions: 1.9
Reporter: Vasiliy Sisko
Priority: Minor


After execution of explain query start of refresh rate will execute explain 
query with specified frequency.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

New documentation domain for tooling

[Denis Magda]

Igniters,

Let me introduce a new documentation domain for Ignite’s tooling:
https://apacheignite-tools.readme.io/docs/ignite-web-console

Presently, there you will find docs for Web Console, Visor CLI, Zeppelin & 
Tableau integrations.

*Prachi*, could you review the following pages?
https://apacheignite-tools.readme.io/docs/getting-started
https://apacheignite-tools.readme.io/docs/build-and-deploy

—
Denis

Re: IGNITE-2626 is cloned?

[Denis Magda]

Taras, Vovan,

Did IGNITE-3191 [1] automatically solve the problem described in [2]? If it’s 
so I would close [2].

BTW, did we add a new configuration parameter as a part of [1] dev activity?

[1] https://issues.apache.org/jira/browse/IGNITE-3191
[2] https://issues.apache.org/jira/browse/IGNITE-2626

—
Denis

> On Feb 16, 2017, at 4:31 AM, ALEKSEY KUZNETSOV  
> wrote:
> 
> Hi! about https://issues.apache.org/jira/browse/IGNITE-2626. Im sure this
> ticket is cloned from https://issues.apache.org/jira/browse/IGNITE-3191,
> because it was implemented there. And im confused with code status : fields
> order is somehow deprecated. This ticket -
> https://issues.apache.org/jira/browse/IGNITE-4695 must have covered fields
> order.
> -- 
> 
> *Best Regards,*
> 
> *Kuznetsov Aleksey*

Re: New documentation domain for tooling

[Denis Magda]

BTW, you don’t need to bookmark this new documentation domain.

Just go to the main one:
https://apacheignite.readme.io/docs/

and in the header you’ll find tabs for all distinct docs we have - .NET, C++, 
Spark, Integrations and Tools.

—
Denis

> On Feb 16, 2017, at 7:52 PM, Denis Magda  wrote:
> 
> Igniters,
> 
> Let me introduce a new documentation domain for Ignite’s tooling:
> https://apacheignite-tools.readme.io/docs/ignite-web-console
> 
> Presently, there you will find docs for Web Console, Visor CLI, Zeppelin & 
> Tableau integrations.
> 
> *Prachi*, could you review the following pages?
> https://apacheignite-tools.readme.io/docs/getting-started
> https://apacheignite-tools.readme.io/docs/build-and-deploy
> 
> —
> Denis
> 

Re: error - Failed to wait for partition release future

[Andrey Mashenkov]

Hi Cameron,

It looks like nodes cant see each other.
Would you please attach grid configuration and full logs?


BTW, ignite version on nodes still "ver=1.8.1#20161208-sha1:a8fcb7b2"

On Fri, Feb 17, 2017 at 2:15 AM, Cameron Braid  wrote:

> Ok,  I have moved to using apache ignite 1.8.0 jar and the same issue is
> there.
>
> I don't believe that  it is slow networking that is causing this as it does
> also happen on a single host single node cluster - its hard to reproduce
> but it does happen.
>
> I've included a log from the grid locking up  on a single node grid.
>
> Any ideas on what I can do to stop the cluster from locking up ?
>
> Feb 17 09:09:22 webapp-97-3v11l webapp  85614 WARN
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture
> [exchange-worker-#26%webapp%] Failed to wait for partition release future
> [topVer=AffinityTopologyVersion [topVer=1, minorTopVer=6],
> node=68845172-67fb-4f49-ae81-f3024ef89e66]. Dumping pending objects that
> might be the cause:
> Feb 17 09:09:22 webapp-97-3v11l webapp  85614 WARN
> o.a.i.i.p.c.GridCachePartitionExchangeManager
> [exchange-worker-#26%webapp%]
> Ready affinity version: AffinityTopologyVersion [topVer=1, minorTopVer=5]
> Feb 17 09:09:22 webapp-97-3v11l webapp  85619 WARN
> o.a.i.i.p.c.GridCachePartitionExchangeManager
> [exchange-worker-#26%webapp%]
> Last exchange future: GridDhtPartitionsExchangeFuture [dummy=false,
> forcePreload=false, reassign=false, discoEvt=DiscoveryCustomEvent
> [customMsg=DynamicCacheChangeBatch [reqs=[DynamicCacheChangeRequest
> [deploymentId=d7f09f84a51-923f7cb7-d9c2-46e8-b121-c7fe21e14aa2,
> startCfg=CacheConfiguration [name=query.starRatings.aggregate,
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=2,
> rebalanceTimeout=1, evictPlc=LruEvictionPolicy [max=500, batchSize=1,
> maxMemSize=0, memSize=0, size=0], evictSync=false, evictKeyBufSize=1024,
> evictSyncConcurrencyLvl=4, evictSyncTimeout=1, evictFilter=null,
> evictMaxOverflowRatio=10.0, eagerTtl=true, dfltLockTimeout=0,
> startSize=150, nearCfg=null, writeSync=PRIMARY_SYNC, storeFactory=null,
> storeKeepBinary=false, loadPrevVal=false,
> aff=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction@3cfe01ec,
> cacheMode=REPLICATED, atomicityMode=ATOMIC, atomicWriteOrderMode=PRIMARY,
> backups=2147483647, invalidate=false, tmLookupClsName=null,
> rebalanceMode=ASYNC, rebalanceOrder=0, rebalanceBatchSize=524288,
> rebalanceBatchesPrefetchCount=2, offHeapMaxMem=-1, swapEnabled=false,
> maxConcurrentAsyncOps=500, writeBehindEnabled=false,
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000,
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, maxQryIterCnt=1024,
> memMode=ONHEAP_TIERED,
> affMapper=o.a.i.i.processors.cache.CacheDefaultBinaryAffinityKeyM
> apper@387ac79,
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null,
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true,
> nodeFilter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate@
> 2a423797,
> sqlSchema=null, sqlEscapeAll=false, sqlOnheapRowCacheSize=10240,
> snapshotableIdx=false, cpOnRead=true, topValidator=null], cacheType=USER,
> initiatingNodeId=68845172-67fb-4f49-ae81-f3024ef89e66, nearCacheCfg=null,
> clientStartOnly=false, stop=false, close=false, failIfExists=true,
> template=false, rcvdFrom=null, exchangeNeeded=true, cacheFutTopVer=null,
> cacheName=query.starRatings.aggregate]], clientNodes=null,
> id=e7f09f84a51-923f7cb7-d9c2-46e8-b121-c7fe21e14aa2,
> clientReconnect=false], affTopVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=6], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=68845172-67fb-4f49-ae81-f3024ef89e66, addrs=[0:0:0:0:0:0:0:1%lo,
> 10.129.1.132, 127.0.0.1], sockAddrs=[webapp-97-3v11l/10.129.1.132:47500,
> /0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1487282891381, loc=true,
> ver=1.8.1#20161208-sha1:a8fcb7b2, isClient=false], topVer=1,
> nodeId8=68845172, msg=null, type=DISCOVERY_CUSTOM_EVT,
> tstamp=1487282952548]], crd=TcpDiscoveryNode
> [id=68845172-67fb-4f49-ae81-f3024ef89e66, addrs=[0:0:0:0:0:0:0:1%lo,
> 10.129.1.132, 127.0.0.1], sockAddrs=[webapp-97-3v11l/10.129.1.132:47500,
> /0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500], discPort=47500, order=1,
> intOrder=1, lastExchangeTime=1487282891381, loc=true,
> ver=1.8.1#20161208-sha1:a8fcb7b2, isClient=false],
> exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion
> [topVer=1, minorTopVer=6], nodeId=68845172, evt=DISCOVERY_CUSTOM_EVT],
> added=true, initFut=GridFutureAdapter [resFlag=0, res=null,
> startTime=1487282952548, endTime=0, ignoreInterrupts=false, state=INIT],
> init=false, topSnapshot=null, lastVer=null,
> partReleaseFut=GridCompoundFuture [rdc=null, initFlag=1, lsnrCalls=3,
> done=false, cancelled=false, err=null, futs=[true, true, true, false]],
> affChangeMsg=null, skipPreload=false, clientOnlyExchange=false,
> initTs=1487282952548, centralizedAff=false, evtLatch=0, remaining=[],
> sr

[jira] [Created] (IGNITE-4715) SQL: FullText index can't be disabled for cache with String values.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-4715:


 Summary: SQL: FullText index can't be disabled for cache with 
String values. 
 Key: IGNITE-4715
 URL: https://issues.apache.org/jira/browse/IGNITE-4715
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 1.8
Reporter: Andrew Mashenkov
 Fix For: 2.0
 Attachments: FullTextIndexTest.java

There is no way to use Sorted only index for cache with String values.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

FullText index can't be disabled for cache with String values.

[Andrey Mashenkov]

Igniters,

I've found that we can't use SORTED index only for cache with String
values.
FULLTEXT index has always being created in
IgniteH2Indexing.TableDescriptor.createIndexes().

I've create a ticket IGNITE-4715 [1]. Serji, please, take a look at this.

[1] https://issues.apache.org/jira/browse/IGNITE-4715

-- 
Best regards,
Andrey V. Mashenkov

Re: IGNITE-2626 is cloned?

[Vladimir Ozerov]

Yes, IGNITE-3191 resolves the problem mentioned in IGNITE-2626. No
configuration parameter needed. We have system property to control this,
but only for compatibility reasons - without it users might have lost
ability to migrate from [1.x] to 1.[x+1] if they persist objects outside of
Ignite.

On Fri, Feb 17, 2017 at 7:11 AM, Denis Magda  wrote:

> Taras, Vovan,
>
> Did IGNITE-3191 [1] automatically solve the problem described in [2]? If
> it’s so I would close [2].
>
> BTW, did we add a new configuration parameter as a part of [1] dev
> activity?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-3191
> [2] https://issues.apache.org/jira/browse/IGNITE-2626
>
> —
> Denis
>
> > On Feb 16, 2017, at 4:31 AM, ALEKSEY KUZNETSOV 
> wrote:
> >
> > Hi! about https://issues.apache.org/jira/browse/IGNITE-2626. Im sure
> this
> > ticket is cloned from https://issues.apache.org/jira/browse/IGNITE-3191,
> > because it was implemented there. And im confused with code status :
> fields
> > order is somehow deprecated. This ticket -
> > https://issues.apache.org/jira/browse/IGNITE-4695 must have covered
> fields
> > order.
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
>
>

Re: DML data streaming

[Vladimir Ozerov]

Dima,

Value type name doesn't necessarily maps to table name. For instance, what
if I have two tables like this? They both have "java.lang.Long" as type
name.

CREATE table *t1* {
pk_id BIGINT PRIMARY KEY,
val BIGINT
}

CREATE table *t2* {
pk_id BIGINT PRIMARY KEY,
val BIGINT
}

On Fri, Feb 17, 2017 at 12:40 AM, Dmitriy Setrakyan 
wrote:

> Vladimir, I am not sure I understand your point. The value type name should
> be the table name, no?
>
> On Thu, Feb 16, 2017 at 12:13 AM, Vladimir Ozerov 
> wrote:
>
> > Dima,
> >
> > At this point we require the following additional data which is outside
> of
> > standard SQL:
> > - Key type
> > - Value type
> > - Set of key columns
> >
> > I do not know yet how we will define these values. At the very least we
> can
> > calculate them automatically in some cases. For "keyFieldName" and
> > "valFieldName" things are easier, as we can always derive them from table
> > definition.
> >
> > Example 1 - primitives:
> >
> > CREATE TABLE (
> > *pk_id* BIGINT PRIMARY KEY,
> > *val*   BIGINT
> > )
> >
> > keyFieldName = "*pk_id*", valFieldName = "*val*"
> >
> > Example 2 - composites:
> >
> > CREATE TABLE (
> > *pk_id* BIGINT PRIMARY KEY,
> > val1  BIGINT,
> > val2  VARCHAR
> > )
> >
> > keyFieldName = "*pk_id*", valFieldName = null (because value is complex
> and
> > is composed of two attributes).
> >
> > Vladimir.
> >
> >
> > On Wed, Feb 15, 2017 at 11:42 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > wrote:
> >
> > > On Wed, Feb 15, 2017 at 4:28 AM, Vladimir Ozerov  >
> > > wrote:
> > >
> > > > Ok, let's put aside current fields configuration, I'll create
> separate
> > > > thread for it. As far as _KEY and _VAL, proposed change is exactly
> > about
> > > > mappings:
> > > >
> > > > class QueryEntity {
> > > > ...
> > > > String keyFieldName;
> > > > String valFieldName;
> > > > ...
> > > > }
> > > >
> > > > The key thing is that we will not require users to be aware of our
> > system
> > > > columns. Normally user should not bother about existence of hidden
> _KEY
> > > and
> > > > _VAL columns. Instead, we just allow them to optionally reference the
> > > whole
> > > > key and/or val through predefined name.
> > > >
> > > >
> > > Vladimir, how will it work from the DDL perspective. Let's say whenever
> > > user wants to create a table in Ignite?
> > >
> >
>