date:20161124

Re: [VOTE] Use Upsource for Code Review

2016-11-24 Thread Vladimir Ozerov

Igniters,

As I understand nobody is forced to use this tool, right?

On Fri, Nov 25, 2016 at 12:01 AM, Konstantin Boudnik  wrote:

> On Mon, Nov 21, 2016 at 12:57PM, Dmitriy Setrakyan wrote:
> > Cos, I see your point, but I think this one falls under procedural issue,
> > no?
>
> Not really. We are talking about a use of a tool to improve the review
> process. Dictating a tool would be a step to a wrong direction. It's like
> imposing the use of IDEA and banishing all Eclipse users (although, I
> wouldn't
> mind really ;)
>
> Dictation of a development technology is where the rift happens, IMO. But
> when
> we are on the same page as the result of the consensus, rather than a fiat
> -
> that's a different story.
>
> Cos
>
> k On Mon, Nov 21, 2016 at 12:21 PM, Konstantin Boudnik 
> wrote:
> >
> > > What are we voting for this?
> > >
> > > Fortunately, Apache isn't about democracy. [1]
> > >
> > > [1] https://www.apache.org/foundation/voting.html
> > >
> > > Cos
> > >
> > > On Wed, Nov 16, 2016 at 01:08PM, Pavel Tupitsyn wrote:
> > > > Following the discussion on Upsource [1],
> > > > I would like to call a vote on accepting it as our official code
> review
> > > > tool.
> > > >
> > > > [ ] +1  approve
> > > > [ ] +0  no opinion
> > > > [ ] -1  disapprove (and reason why)
> > > >
> > > > This vote will go on for 5 days.
> > > >
> > > > [1] http://apache-ignite-developers.2346864.n4.nabble.
> > > > com/Code-Review-Tool-Proposal-Upsource-td12195.html
> > >
>

Re: [VOTE] Use Upsource for Code Review

2016-11-24 Thread Konstantin Boudnik

On Mon, Nov 21, 2016 at 12:57PM, Dmitriy Setrakyan wrote:
> Cos, I see your point, but I think this one falls under procedural issue,
> no?

Not really. We are talking about a use of a tool to improve the review
process. Dictating a tool would be a step to a wrong direction. It's like
imposing the use of IDEA and banishing all Eclipse users (although, I wouldn't
mind really ;)

Dictation of a development technology is where the rift happens, IMO. But when
we are on the same page as the result of the consensus, rather than a fiat -
that's a different story.

Cos

k On Mon, Nov 21, 2016 at 12:21 PM, Konstantin Boudnik  wrote:
> 
> > What are we voting for this?
> >
> > Fortunately, Apache isn't about democracy. [1]
> >
> > [1] https://www.apache.org/foundation/voting.html
> >
> > Cos
> >
> > On Wed, Nov 16, 2016 at 01:08PM, Pavel Tupitsyn wrote:
> > > Following the discussion on Upsource [1],
> > > I would like to call a vote on accepting it as our official code review
> > > tool.
> > >
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > > This vote will go on for 5 days.
> > >
> > > [1] http://apache-ignite-developers.2346864.n4.nabble.
> > > com/Code-Review-Tool-Proposal-Upsource-td12195.html
> >

Re: Apache Ignite 1.8 Release

2016-11-24 Thread Sergey Kozlov

Hi

I found two issues for 1.8:
IGNITE-4304 ClusterTopologyCheckedException: Failed to send message because
node left grid 
IGNITE-4303 CacheClientBinaryQueryExample returns wrong result


Could someone experienced take a look?

On Thu, Nov 24, 2016 at 12:12 PM, Vladimir Ozerov 
wrote:

> Folks,
>
> DML is merged to ignite-1.8, but according to JIRA reports several problems
> with it were revealed. I propose to focus on DML finalization in ignite-1.8
> branch, and minimize other merges to it, targeting them for the next
> release (1.9, 2.0?).
>
> Any objections?
>
> Vladimir.
>
> On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego  wrote:
>
> > Denis,
> >
> > I've raised PRs and Vladimir has merged them into ignite-1.8. But now we
> > have some
> > failing ODBC tests in the branch. I'm currently working on them. There
> is a
> > ticket for
> > that which you can track [1]. I'll add all my findings there.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-4288
> >
> > Best Regards,
> > Igor
> >
> > On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda  wrote:
> >
> > > Alexander,
> > >
> > > Awesome news, thanks for making this happen!
> > >
> > > Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I
> > start
> > > testing that PHP-PDO guidance [1] is correct?
> > >
> > > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> > > https://apacheignite.readme.io/docs/pdo-interoperability>
> > >
> > > —
> > > Denis
> > >
> > > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > > alexander.a.pasche...@gmail.com> wrote:
> > > >
> > > > Folks,
> > > >
> > > > Yesterday it'd been agreed with Sergi that DML branch is now good to
> > > > be included into 1.8 branch that is to be created.
> > > >
> > > > Minor review fixes, should they be made, and test fixes will be
> > > > incorporated into 1.8 as separate patches later.
> > > >
> > > > Also, it'd been agreed that, in order to deliver these new features
> on
> > > > time, two subtasks will be fixed in later releases (shortly):
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-4268
> > > > https://issues.apache.org/jira/browse/IGNITE-4269
> > > >
> > > > On failing tests:
> > > > https://issues.apache.org/jira/browse/IGNITE-2294?
> > > focusedCommentId=15683377
> > > >
> > > > - Alex
> > > >
> > > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > > > :
> > > >> Vlad,
> > > >>
> > > >> Most likely today.
> > > >>
> > > >> - Alex
> > > >>
> > > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> > > >>> Igniters,
> > > >>>
> > > >>> I went through remaining tickets assigned to 1.8 and it seems that
> we
> > > are
> > > >>> pretty close to release. As far as I understand the biggest
> remaining
> > > >>> feature is DML [1]. I think we can create separate branch for 1.8
> as
> > > soon
> > > >>> as it is merged. Alex, do you have any idea on when it might
> happen?
> > > >>>
> > > >>> Vladimir.
> > > >>>
> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> > > >>>
> > > >>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
> > > wrote:
> > > >>>
> > >  Roman,
> > > 
> > >  That versions will be created after 1.8 gets released. Recently
> > there
> > > was
> > >  a discussion on the dev list [1] regarding the difficulties
> related
> > to
> > >  documentation maintenance when several documentation versions
> > > co-exist at
> > >  the same time.
> > > 
> > >  It was decided that rather then create a new version for the
> > > documentation
> > >  once a new feature added to Ignite it’s better to create a hidden
> > page
> > >  under the current documentation version and make it visible once
> the
> > > next
> > >  version is created after the release.
> > > 
> > >  The bottom line is that, please create a hidden page with a suffix
> > >  “page_name-1.8” and once 1.8 gets released Prachi will create
> > > readme.io <
> > >  http://readme.io/> 1.8 and make your doc visible.
> > > 
> > >  [1] http://apache-ignite-developers.2346864.n4.nabble.
> > >  com/Maintaining-documentation-consistency-on-readme-io-
> td10868.html
> > <
> > >  http://apache-ignite-developers.2346864.n4.nabble.
> > >  com/Maintaining-documentation-consistency-on-readme-io-
> > td10868.html>
> > > 
> > >  —
> > >  Denis
> > > 
> > > > On Nov 16, 2016, at 5:00 PM, Roman Shtykh
> >  > > >
> > >  wrote:
> > > >
> > > > Denis,
> > > > Any plans to add 1.8.0 in readme.io for new features?
> > > > -Roman
> > > >   On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
> > >  dma...@apache.org> wrote:
> > > >
> > > >
> > > > Igor,
> > > >
> > > > It makes sense

[jira] [Created] (IGNITE-4304) CLONE - CacheClientBinaryQueryExample returns wrong result

2016-11-24 Thread Sergey Kozlov (JIRA)

Sergey Kozlov created IGNITE-4304:
-

 Summary: CLONE - CacheClientBinaryQueryExample returns wrong result
 Key: IGNITE-4304
 URL: https://issues.apache.org/jira/browse/IGNITE-4304
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


CacheClientBinaryQueryExample returns wrong result: the list of GridGain 
employees must be not empty.

{noformat}
>>> Employees working for GridGain:

>>> Employee names and their salaries:
>>> [Name=Allison Mathis, salary=25300]
>>> [Name=Breana Robbin, salary=6500]
>>> [Name=Philip Horsley, salary=19800]
>>> [Name=Brian Peters, salary=10600]
>>> [Name=James Wilson, salary=12500]
>>> [Name=Daniel Adams, salary=11000]
>>> [Name=Cristian Moss, salary=12500]
{noformat}

Also the server node print out following:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4303) CacheClientBinaryQueryExample returns wrong result

2016-11-24 Thread Sergey Kozlov (JIRA)

Sergey Kozlov created IGNITE-4303:
-

 Summary: CacheClientBinaryQueryExample returns wrong result
 Key: IGNITE-4303
 URL: https://issues.apache.org/jira/browse/IGNITE-4303
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


CacheClientBinaryQueryExample returns wrong result: the list of GridGain 
employees must be not empty.

{noformat}
>>> Employees working for GridGain:

>>> Employee names and their salaries:
>>> [Name=Allison Mathis, salary=25300]
>>> [Name=Breana Robbin, salary=6500]
>>> [Name=Philip Horsley, salary=19800]
>>> [Name=Brian Peters, salary=10600]
>>> [Name=James Wilson, salary=12500]
>>> [Name=Daniel Adams, salary=11000]
>>> [Name=Cristian Moss, salary=12500]
{noformat}

Also the server node print out following:
{noformat}
[22:46:53,052][ERROR][sys-#65%null%][IgniteTxManager] Failed to send one phase 
commit ack to backup node [backup=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException: 
Failed to send message because node left grid 
[nodeId=c8d7e7b7-d984-4498-ab4c-8e7cb8928e19, 
msg=GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=91496812, 
time=1480016812498, order=1480016808989, nodeOrder=1]], super=GridCacheMessage 
[msgId=-1, depInfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1056)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at 
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6620)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:764)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #1281: Ignite 4026

2016-11-24 Thread dkarachentsev

GitHub user dkarachentsev opened a pull request:

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

Ignite 4026



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

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

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

https://github.com/apache/ignite/pull/1281.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 #1281


commit dfc728817c3cd3512760bc7383b747e8b4f8b13d
Author: Pavel Tupitsyn 
Date:   2016-09-23T16:18:26Z

IGNITE-3199 .NET: ASP.NET Session-State Store Provider - fix javadoc

commit 8e996796279eb31cd167cdd10e32f71a8efaca27
Author: Pavel Tupitsyn 
Date:   2016-09-23T16:28:56Z

.NET: Fix analysis warnings

commit 14959f2efea43046a1a2e5c1978fc27a156f5a7a
Author: vozerov-gridgain 
Date:   2016-09-26T07:12:45Z

IGNITE-3925: Removed unnecessary "log.isInfoEnabled()" check during PID 
printout.

commit 990fa0908966b71ab7340a4906e9937e32a6e78a
Author: Alexey Kuznetsov 
Date:   2016-09-26T07:22:32Z

Merge ignite-1.6.9 into ignite-1.7.2.

commit 3a66596d76eae5b9265a7de74faeae812d95
Author: ptupitsyn 
Date:   2016-09-26T08:00:25Z

IGNITE-3291 .NET: Added IClusterGroup.ForDaemons() method. This closes 
#1094.

commit 38d1d0491ab9e6858a58b90d0e5d892d9fc0e284
Author: Igor Sapego 
Date:   2016-09-26T08:04:56Z

IGNITE-3876: ODBC: Better handling of NULL values for output parameters. 
This closes #1099.

commit 548fe6a3fe4d38caebe3b45366f3e812b035d006
Author: tledkov-gridgain 
Date:   2016-09-26T09:05:07Z

IGNITE-: IGFS: Now it is possible to use ATOMIC cache for data blocks 
when fragmentizer it disabled. This closes #1108.

commit 8032fc2c8a7cf9f404eb75c65164bb2900aab79d
Author: vozerov-gridgain 
Date:   2016-09-26T09:31:30Z

IGNITE-3912: Hadoop: Implemented new class loading architecture for 
embedded execution mode.

commit 33a6878eccd60f86648067901613b713ef3bb71f
Author: Pavel Tupitsyn 
Date:   2016-09-26T11:56:51Z

IGNITE-3491 .NET: Allow type name without assembly for type properties in 
app.config

commit 4f9ac81c5d88f333d9aec78cc480230c48fd88f2
Author: Pavel Tupitsyn 
Date:   2016-09-26T12:06:34Z

Merge remote-tracking branch 'remotes/community/ignite-1.6.9' into 
ignite-1.7.2

commit a4a933eb708dadb6b67f6c062db32ffeef819184
Author: Igor Sapego 
Date:   2016-09-26T14:41:57Z

IGNITE-3883: ODBC: Implemented data-at-execution dialog. This closes #1073.

commit 350e84656686eb81f8e12d569783db9914ca5a37
Author: Pavel Tupitsyn 
Date:   2016-09-26T16:55:27Z

IGNITE-3956 .NET: Fix cache creation in LINQPad examples
This closes #1116

commit bbc97580492609e2e4fc3d92b08b4740b984d78f
Author: isapego 
Date:   2016-09-26T17:17:43Z

Merge branch 'ignite-1.6.9' into ignite-1.7.2

commit 6a41dc92da124a921b304392e922886c30597037
Author: Saikat Maitra 
Date:   2016-09-26T22:28:51Z

IGNITE-3807 IgniteSpiContext registers message listeners incorrectly

commit 5ff9e5e8c95ea0fe37d281a7ff46e148469f952a
Author: Saikat Maitra 
Date:   2016-09-26T22:28:51Z

IGNITE-3807 IgniteSpiContext registers message listeners incorrectly

commit 97bfee4dff807e3049b61fa473472a8395cdcb6a
Author: vozerov-gridgain 
Date:   2016-09-27T07:06:48Z

Fixing RAT.

commit 0dac458d2aa36b03986412726bd607877e53aa4f
Author: vozerov-gridgain 
Date:   2016-09-27T07:07:03Z

Merge remote-tracking branch 'upstream/ignite-1.6.9' into ignite-1.6.9

commit 68b0bcd83c295ce540aa9d9d0910abcf671671df
Author: Pavel Tupitsyn 
Date:   2016-09-27T09:08:46Z

IGNITE-3970 .NET: Fix Cyrillic 'C' letters in code

commit 41df266a232afd86ade91c5e18f082206913007c
Author: Pavel Tupitsyn 
Date:   2016-09-27T09:14:01Z

Merge remote-tracking branch 'remotes/community/ignite-1.6.9' into 
ignite-1.7.2

commit 48d4a9252536dd82811a10327b2df6ddbd1ff13a
Author: Alexey Kuznetsov 
Date:   2016-09-27T10:03:36Z

Web console beta-4.

commit 29acb33293c3d3130e16b7ff4d6b7ae260b7b78b
Author: Alexey Kuznetsov 
Date:   2016-09-27T10:15:38Z

Fixed typos.

commit 3f62596ec33026fb6104f7ed33979a0df46c5789
Author: Alexey Kuznetsov 
Date:   2016-09-27T10:19:00Z

Merge ignite-1.6.9 into ignite-1.7.2.

commit c2a3f11ca14cf9f9cf5bd2d6e2a87764f7cda5a7
Author: Andrey Martianov 
Date:   2016-09-20T14:41:49Z

ignite-3621 Use single ttl cleanup worker thread for all caches

[GitHub] ignite pull request #1280: IGNITE-4287 DmlStatementsProcessor logic fix

2016-11-24 Thread alexpaschenko

GitHub user alexpaschenko opened a pull request:

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

IGNITE-4287 DmlStatementsProcessor logic fix



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

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

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

https://github.com/apache/ignite/pull/1280.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 #1280


commit 63a36224d30f3d7626770e6a35a9eac05e370290
Author: Alexander Paschenko 
Date:   2016-11-24T06:09:45Z

IGNITE-4287 DmlStatementsProcessor logic fix (always force keepBinary for 
SELECTs inside DML logic)




---
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-4302) Use discovery custom messages instead of system cache

2016-11-24 Thread Sergey Chugunov (JIRA)

Sergey Chugunov created IGNITE-4302:
---

 Summary: Use discovery custom messages instead of system cache
 Key: IGNITE-4302
 URL: https://issues.apache.org/jira/browse/IGNITE-4302
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
 Fix For: 2.0


h4. Notes
See [IGNITE-4157|https://issues.apache.org/jira/browse/IGNITE-4157] for more 
details about context.

h4. Acceptance Criteria
# Binary metadata cache is deleted.
# Binary metadata exchange is performed using *DiscoveryCustomMessage* events.






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4301) Hadoop: put shuffle ack to the top of send queue.

2016-11-24 Thread Vladimir Ozerov (JIRA)

Vladimir Ozerov created IGNITE-4301:
---

 Summary: Hadoop: put shuffle ack to the top of send queue.
 Key: IGNITE-4301
 URL: https://issues.apache.org/jira/browse/IGNITE-4301
 Project: Ignite
  Issue Type: Sub-task
  Components: general, hadoop
Affects Versions: 1.7, 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


This shuffle acks will be processed ASAP, hence minimizing wait during 
completion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #1279: gg-8.0.1.ea7

2016-11-24 Thread agoncharuk

GitHub user agoncharuk opened a pull request:

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

gg-8.0.1.ea7



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

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-8.0.1.ea7

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

https://github.com/apache/ignite/pull/1279.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 #1279


commit ec49b2c9dbc1c734cb00d6e85938285513ce4d99
Author: sboikov 
Date:   2016-09-13T05:07:59Z

ignite-db-x-free1

commit 162b7ead8fde611bd5e3b3776ac19af8885da1a0
Author: sboikov 
Date:   2016-09-13T06:06:32Z

Merge remote-tracking branch 'community/ignite-db-x-free1' into 
ignite-db-x-free1

commit 9cfc1dd1044fab75dc321058a752eea20239d365
Author: Alexey Goncharuk 
Date:   2016-09-13T07:53:17Z

GG-10882 - Messages re-generated

commit 91836cd7c8486e4beec8161a4321d2e2a17d1f89
Author: sboikov 
Date:   2016-09-13T07:41:57Z

ignite-db-x-free1

commit 5e013a6c83f6252aec301618e107631e3d1ee14e
Author: Alexey Goncharuk 
Date:   2016-09-13T08:04:07Z

Merge branch 'ignite-db-x' of https://github.com/gridgain/apache-ignite 
into ignite-gg-8.0.0.ea1

commit 63719c7bbca3b894e5018b5305d99f18509fe860
Author: Alexey Goncharuk 
Date:   2016-09-13T08:48:37Z

Merge branch 'ignite-gg-8.0.0.ea1' of 
https://github.com/gridgain/apache-ignite into ignite-gg-8.0.0.ea1

commit 6070566ce2bc69ba732cda92dc899eea81175648
Author: sboikov 
Date:   2016-09-13T09:47:21Z

db-x-free1

commit 3ba8328e8b39dc2027b12584b029e85d599deb0c
Author: sboikov 
Date:   2016-09-13T09:32:51Z

11289

commit 2e82ce0acebf4ff7553428231b918a334956a99a
Author: EdShangGG 
Date:   2016-09-13T11:57:50Z

GG-11503 WAL history is too short / NPE upon repetitive node restarts

commit a68bbd39023d8d68786a660aa395dddec3394388
Author: Alexey Goncharuk 
Date:   2016-09-13T12:01:30Z

Merge branch 'ignite-gg-10882' into ignite-gg-8.0.0.ea1

commit a13bb3eed61a0cc84856eda274abb70ab8fa258e
Author: Alexey Goncharuk 
Date:   2016-09-13T12:01:49Z

Merge branch 'ignite-gg-10882' into ignite-gg-8.0.0.ea1

commit 86878562536fa20596a656df62906a23d8b077f4
Author: EdShangGG 
Date:   2016-09-13T12:29:47Z

GG-11503 WAL history is too short / NPE upon repetitive node restarts
-fixes in PageIO.getPageIO

commit a3c22b9f3332ee5e4059228bb803c06d43fcdf88
Author: sboikov 
Date:   2016-09-13T13:20:57Z

ignite-db-x-free1

commit e1062a0b364a1922a11ac2ea2828ed2b266e108f
Author: Sergi Vladykin 
Date:   2016-09-13T13:38:00Z

ignite-db-x - btree fixes

commit dd8e0af3538c40a56409cfdea46a0b897c420cc2
Author: sboikov 
Date:   2016-09-13T13:50:11Z

ignite-db-x-free1

commit 887bf2da41d8b0eecd47597d7c3c128d69330080
Author: sboikov 
Date:   2016-09-13T13:50:54Z

Merge branch 'ignite-db-x-free1' into db-x-free-11289

commit 34568eda31516ed52195cb54ecbaf7a9e84ab4b2
Author: sboikov 
Date:   2016-09-13T14:21:28Z

GG-11386 Change data structure in ReuseList (merge with new FreeList)

commit df8d93ae83413f31a95bed9b3c1483fefa74455c
Author: Ilya Lantukh 
Date:   2016-09-13T14:22:07Z

gg-11427 : Partition state recovery from meta pages.

commit 78c13886dd1288ade8d76966ac228c8f5b35ecd3
Author: Ilya Lantukh 
Date:   2016-09-13T14:59:48Z

gg-11427 : Merge.

commit 18ab8faf5a9962a43a97a4ccc931f28635fd790a
Author: Ilya Lantukh 
Date:   2016-09-13T15:15:58Z

gg-11427 : Merge.

commit 4a932d8a8fc8ebc584d16fa2c06dfa98da9b8b99
Author: Ilya Lantukh 
Date:   2016-09-13T15:23:32Z

gg-11427 : Cosmetic changes.

commit 74736c26566d9b8e29a7f37064daffefc1aa88b0
Author: Ilya Lantukh 
Date:   2016-09-13T16:12:49Z

db-x: Fixed partition eviction.

commit 5748cc3fb9095599137316ae018eb1869af88809
Author: EdShangGG 
Date:   2016-09-13T17:04:04Z

GG-11442 Failing test in db-x branch

commit 8df1454df482f40832e5be4be1f70fb2b2c8235d
Author: Alexey Goncharuk 
Date:   2016-09-13T17:24:28Z

GG-11503 - Fixed recovery from WAL

commit cb716cee7c44bc91f6dbf70fdf12aff8e95bc27c
Author: Alexey Goncharuk 
Date:   2016-09-13T17:24:41Z

Merge branch 'ignite-gg-8.0.0.ea1' of 
https://github.com/gridgain/apache-ignite into ignite-gg-11503

commit a8b3bb425fb08783a725b63271308e1244350d22
Author: Alexey Goncharuk

[jira] [Created] (IGNITE-4300) Hadoop: get rid of shuffle job.

2016-11-24 Thread Vladimir Ozerov (JIRA)

Vladimir Ozerov created IGNITE-4300:
---

 Summary: Hadoop: get rid of shuffle job.
 Key: IGNITE-4300
 URL: https://issues.apache.org/jira/browse/IGNITE-4300
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


1) When mapper detects that 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #1278: IGNITE-4106: SQL: parallelize sql queries over ca...

2016-11-24 Thread AMashenkov

GitHub user AMashenkov opened a pull request:

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

IGNITE-4106: SQL: parallelize sql queries over cache local partitions

Indexes splitted

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

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

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

https://github.com/apache/ignite/pull/1278.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 #1278


commit cede430c27f1bc73a3fd61a3569c164d16869816
Author: Andrey V. Mashenkov 
Date:   2016-11-18T12:19:33Z

Merged

commit e8329f93003c77d1070cf88be3cbaf19e7845656
Author: Andrey V. Mashenkov 
Date:   2016-11-18T12:47:05Z

index splitted

commit 4e88be252ce35482ac4b885e8e97b7fa16d3e53b
Author: Andrey V. Mashenkov 
Date:   2016-11-24T12:46:15Z

Merge remote-tracking branch 'apache/master' into ignite-4106-2

# Conflicts:
#   
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/twostep/GridMergeIndex.java




---
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 #1277: IGNITE-4299: Fixes for examples.

2016-11-24 Thread isapego

GitHub user isapego opened a pull request:

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

IGNITE-4299: Fixes for examples.



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

$ git pull https://github.com/isapego/ignite ignite-4299

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

https://github.com/apache/ignite/pull/1277.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 #1277


commit 1403c6438d5d5263d98b3796d15cd65faff8845b
Author: Igor Sapego 
Date:   2016-11-24T12:37:32Z

IGNITE-4299: Fixes for examples.




---
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-4299) Remove useless cin.get() in query_example.cpp

2016-11-24 Thread Ksenia Rybakova (JIRA)

Ksenia Rybakova created IGNITE-4299:
---

 Summary: Remove useless cin.get() in query_example.cpp
 Key: IGNITE-4299
 URL: https://issues.apache.org/jira/browse/IGNITE-4299
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Reporter: Ksenia Rybakova
Priority: Minor


Remove useless cin.get() in query_example.cpp:
{noformat}
std::cout << ">>> Ready" << std::endl;
std::cout << std::endl;
std::cin.get();
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #1276: IGNITE-4297 .NET: Update NuGet uninstall script t...

2016-11-24 Thread ptupitsyn

GitHub user ptupitsyn opened a pull request:

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

IGNITE-4297 .NET: Update NuGet uninstall script to clean up jars



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

$ git pull https://github.com/ptupitsyn/ignite ignite-4297

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

https://github.com/apache/ignite/pull/1276.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 #1276


commit 226278bd748b7598749732a9a4e424147ce98fef
Author: Pavel Tupitsyn 
Date:   2016-11-24T11:53:29Z

IGNITE-4297 .NET: Update uninstall script to clean up jars




---
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-4298) User exceptions cause IgniteException if Ignite services are deployed separately

2016-11-24 Thread Ben (JIRA)

Ben created IGNITE-4298:
---

 Summary: User exceptions cause IgniteException if Ignite services 
are deployed separately
 Key: IGNITE-4298
 URL: https://issues.apache.org/jira/browse/IGNITE-4298
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Ben


2 services, Service A and Service B, are deployed and restricted to individual 
nodes. If A calls a method of B thru the service proxy and a user exception is 
thrown inside that method, then an IgniteException is thrown due to an 
InvocationTargetException. See code below for a reproducable example.

{code:title=MyUserException.java|borderStyle=solid}
package com.example.testing;

public class MyUserException extends Throwable {}
{code}

{code:title=MyCounterService.java|borderStyle=solid}
package com.example.testing;

public interface MyCounterService {
int increment() throws MyUserException;
}
{code}

Note this error condition in the deployment of the two services: 
{{ignite.cluster().forYoungest()}}

{code:title=MyCounterServiceImpl.java|borderStyle=solid}
package com.example.testing;

import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteServices;
import org.apache.ignite.Ignition;
import org.apache.ignite.resources.IgniteInstanceResource;
import org.apache.ignite.services.Service;
import org.apache.ignite.services.ServiceContext;

public class MyCounterServiceImpl implements MyCounterService, Service {

@IgniteInstanceResource
private Ignite ignite;

private int value = 0;

public int increment() throws MyUserException {
if ((value % 2) == 0) {
throw new MyUserException();
} else {
value++;
}
return value;
}

public static void main(String [] args) {
Ignite ignite = Ignition.start();
IgniteServices svcs = ignite.services(ignite.cluster().forYoungest());
svcs.deployNodeSingleton("MyCounterService", new 
MyCounterServiceImpl());
}

@Override
public void cancel(ServiceContext ctx) {
System.out.println("Service cancelled");
}

@Override
public void init(ServiceContext ctx) throws Exception {
System.out.println("Service initialized");
}

@Override
public void execute(ServiceContext ctx) throws Exception {
System.out.println("Service running");
}
}
{code}

{code:title=MyCallerService.java|borderStyle=solid}
package com.example.testing;

import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteException;
import org.apache.ignite.Ignition;
import org.apache.ignite.resources.IgniteInstanceResource;
import org.apache.ignite.services.Service;
import org.apache.ignite.services.ServiceContext;

public class MyCallerService implements Service {

@IgniteInstanceResource
private Ignite ignite;

private Boolean stopped;

public void run() {
stopped = false;
MyCounterService service = 
ignite.services().serviceProxy("MyCounterService", MyCounterService.class, 
false);
while (!stopped)
{
try {
Thread.sleep(500);
service.increment();
} catch (MyUserException e) {
System.out.println("Got exception");
//e.printStackTrace();
} catch (InterruptedException e) {
//e.printStackTrace();
}
catch (IgniteException e) {
System.out.println("Got critial exception");
// would print the actual user exception
//e.getCause().getCause().getCause().printStackTrace();
break;
}
}
}

public static void main(String [] args) {
Ignite ignite = Ignition.start();

ignite.services(ignite.cluster().forYoungest()).deployNodeSingleton("MyCallerService",
 new MyCallerService());
}

@Override
public void cancel(ServiceContext ctx) {
stopped = true;
}

@Override
public void init(ServiceContext ctx) throws Exception {

}

@Override
public void execute(ServiceContext ctx) throws Exception {
run();
}
}
{code}

{code:title=Output of MyCounterServiceImpl|borderStyle=solid}
[18:23:23] Ignite node started OK (id=c82df19c)
[18:23:23] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
Service initialized
Service running
[18:23:27] Topology snapshot [ver=2, servers=2, clients=0, CPUs=4, heap=7.0GB]
Nov 17, 2016 6:23:28 PM org.apache.ignite.logger.java.JavaLogger error
SCHWERWIEGEND: Failed to execute job 
[jobId=82580537851-3c0a354f-69b5-496c-af10-ee789a5387c3, ses=GridJobSessionImpl 
[ses=GridTaskSessionImpl 
[taskName=o.a.i.i.processors.service.GridServiceProxy$ServiceProxyCallable, 
dep=LocalDeployment [super=GridDeployment [ts=1479403401422, depMode=SHARED, 
clsLdr=sun.misc.Launcher$AppClassLoader@1d44bcfa,

[jira] [Created] (IGNITE-4297) .NET: Upgrading NuGet to new version does not update jar files in bin folder

2016-11-24 Thread Pavel Tupitsyn (JIRA)

Pavel Tupitsyn created IGNITE-4297:
--

 Summary: .NET: Upgrading NuGet to new version does not update jar 
files in bin folder
 Key: IGNITE-4297
 URL: https://issues.apache.org/jira/browse/IGNITE-4297
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.8


Apache.Ignite.Core NuGet package updates post-build step with a script to copy 
jar files to the bin directory.

However, this script copies jar files only when the bin\libs folder does not 
exist. This causes a problem when upgrading to a new version of NuGet package: 
bin\libs does not get updated, and user gets an error like

{code}
Failed to initialize JVM. ---> Apache.Ignite.Core.Common.IgniteException: Java 
class method is not found (did you set IGNITE_HOME environment variable?): 
binaryProcessor ---> Apache.Ignite.Core.Common.JavaException: 
java.lang.NoSuchMethodError: binaryProcessor
{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Apache Ignite 1.8 Release

2016-11-24 Thread Vladimir Ozerov

Folks,

DML is merged to ignite-1.8, but according to JIRA reports several problems
with it were revealed. I propose to focus on DML finalization in ignite-1.8
branch, and minimize other merges to it, targeting them for the next
release (1.9, 2.0?).

Any objections?

Vladimir.

On Wed, Nov 23, 2016 at 7:25 PM, Igor Sapego  wrote:

> Denis,
>
> I've raised PRs and Vladimir has merged them into ignite-1.8. But now we
> have some
> failing ODBC tests in the branch. I'm currently working on them. There is a
> ticket for
> that which you can track [1]. I'll add all my findings there.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4288
>
> Best Regards,
> Igor
>
> On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda  wrote:
>
> > Alexander,
> >
> > Awesome news, thanks for making this happen!
> >
> > Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I
> start
> > testing that PHP-PDO guidance [1] is correct?
> >
> > [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> > https://apacheignite.readme.io/docs/pdo-interoperability>
> >
> > —
> > Denis
> >
> > > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> > alexander.a.pasche...@gmail.com> wrote:
> > >
> > > Folks,
> > >
> > > Yesterday it'd been agreed with Sergi that DML branch is now good to
> > > be included into 1.8 branch that is to be created.
> > >
> > > Minor review fixes, should they be made, and test fixes will be
> > > incorporated into 1.8 as separate patches later.
> > >
> > > Also, it'd been agreed that, in order to deliver these new features on
> > > time, two subtasks will be fixed in later releases (shortly):
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-4268
> > > https://issues.apache.org/jira/browse/IGNITE-4269
> > >
> > > On failing tests:
> > > https://issues.apache.org/jira/browse/IGNITE-2294?
> > focusedCommentId=15683377
> > >
> > > - Alex
> > >
> > > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > > :
> > >> Vlad,
> > >>
> > >> Most likely today.
> > >>
> > >> - Alex
> > >>
> > >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> > >>> Igniters,
> > >>>
> > >>> I went through remaining tickets assigned to 1.8 and it seems that we
> > are
> > >>> pretty close to release. As far as I understand the biggest remaining
> > >>> feature is DML [1]. I think we can create separate branch for 1.8 as
> > soon
> > >>> as it is merged. Alex, do you have any idea on when it might happen?
> > >>>
> > >>> Vladimir.
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> > >>>
> > >>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
> > wrote:
> > >>>
> >  Roman,
> > 
> >  That versions will be created after 1.8 gets released. Recently
> there
> > was
> >  a discussion on the dev list [1] regarding the difficulties related
> to
> >  documentation maintenance when several documentation versions
> > co-exist at
> >  the same time.
> > 
> >  It was decided that rather then create a new version for the
> > documentation
> >  once a new feature added to Ignite it’s better to create a hidden
> page
> >  under the current documentation version and make it visible once the
> > next
> >  version is created after the release.
> > 
> >  The bottom line is that, please create a hidden page with a suffix
> >  “page_name-1.8” and once 1.8 gets released Prachi will create
> > readme.io <
> >  http://readme.io/> 1.8 and make your doc visible.
> > 
> >  [1] http://apache-ignite-developers.2346864.n4.nabble.
> >  com/Maintaining-documentation-consistency-on-readme-io-td10868.html
> <
> >  http://apache-ignite-developers.2346864.n4.nabble.
> >  com/Maintaining-documentation-consistency-on-readme-io-
> td10868.html>
> > 
> >  —
> >  Denis
> > 
> > > On Nov 16, 2016, at 5:00 PM, Roman Shtykh
>  > >
> >  wrote:
> > >
> > > Denis,
> > > Any plans to add 1.8.0 in readme.io for new features?
> > > -Roman
> > >   On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
> >  dma...@apache.org> wrote:
> > >
> > >
> > > Igor,
> > >
> > > It makes sense to wait for me while everything gets merged into 1.8
> >  then. Please let me know over this discussion when the overall merge
> >  happens.
> > >
> > > —
> > > Denis
> > >
> > >> On Nov 15, 2016, at 1:45 AM, Igor Sapego 
> > wrote:
> > >>
> > >> Denis,
> > >>
> > >> I can merge PDO-related changes into 1.8 but without DML they will
> >  break tests
> > >> and even compilation so I don't see any sense in doing that before
> > DML
> >  is merged.
> > >>
> > >> After DML is ready and merged I'll need some time to merge my
> > changes
> >  and check
> > >> that everything works as intended. The code

[jira] [Created] (IGNITE-4296) Optimize GridDhtPartitionsSingleMessage processing

2016-11-24 Thread Semen Boikov (JIRA)

Semen Boikov created IGNITE-4296:


 Summary: Optimize GridDhtPartitionsSingleMessage processing
 Key: IGNITE-4296
 URL: https://issues.apache.org/jira/browse/IGNITE-4296
 Project: Ignite
  Issue Type: Task
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
 Fix For: 1.9


These optimizations are possible:
- now on exchange GridDhtPartitionsSingleMessage is processed inside exchange 
future exclusive lock
-  GridDhtPartitionTopology.update always creates copies of node2part, 
part2node maps
- it is possible for joning node do not send GridDhtPartitionsSingleMessage 
since we know in advance it does not have any data



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4295) GridUnsafe: implement specialized methods for every kind of copy operation.

2016-11-24 Thread Vladimir Ozerov (JIRA)

Vladimir Ozerov created IGNITE-4295:
---

 Summary: GridUnsafe: implement specialized methods for every kind 
of copy operation.
 Key: IGNITE-4295
 URL: https://issues.apache.org/jira/browse/IGNITE-4295
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Minor
 Fix For: 2.0


1) copy(OFFHEAP, HEAP)
2) copy(HEAP, OFFHEAP)
3) copy(OFFHEAP, OFFHEAP)
4) copy(HEAP, HEAP) 
5) copy(T[], T[]) must be avoided and replaced with System.arrayCopy().
6) Add optional threshold. If we copy too small memory chunk which size is 
below the threshold, then resort to byte-by-byte copying, as it will be faster.

E.g. on PowerPC with OpenJDK 8, copying of <100 bytes of data is faster on 
byte-by-byte basis.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4294) Allow unaligned memory access flag override in GridUnsafe.

2016-11-24 Thread Vladimir Ozerov (JIRA)

Vladimir Ozerov created IGNITE-4294:
---

 Summary: Allow unaligned memory access flag override in GridUnsafe.
 Key: IGNITE-4294
 URL: https://issues.apache.org/jira/browse/IGNITE-4294
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


This way we can avoid byte-by-byte read/write if arch is not x86, but it 
permits unaligned access still.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Use Upsource for Code Review

Re: [VOTE] Use Upsource for Code Review

Re: Apache Ignite 1.8 Release

[jira] [Created] (IGNITE-4304) CLONE - CacheClientBinaryQueryExample returns wrong result

[jira] [Created] (IGNITE-4303) CacheClientBinaryQueryExample returns wrong result

[GitHub] ignite pull request #1281: Ignite 4026

[GitHub] ignite pull request #1280: IGNITE-4287 DmlStatementsProcessor logic fix

[jira] [Created] (IGNITE-4302) Use discovery custom messages instead of system cache

[jira] [Created] (IGNITE-4301) Hadoop: put shuffle ack to the top of send queue.

[GitHub] ignite pull request #1279: gg-8.0.1.ea7

[jira] [Created] (IGNITE-4300) Hadoop: get rid of shuffle job.

[GitHub] ignite pull request #1278: IGNITE-4106: SQL: parallelize sql queries over ca...

[GitHub] ignite pull request #1277: IGNITE-4299: Fixes for examples.

[jira] [Created] (IGNITE-4299) Remove useless cin.get() in query_example.cpp

[GitHub] ignite pull request #1276: IGNITE-4297 .NET: Update NuGet uninstall script t...

[jira] [Created] (IGNITE-4298) User exceptions cause IgniteException if Ignite services are deployed separately

[jira] [Created] (IGNITE-4297) .NET: Upgrading NuGet to new version does not update jar files in bin folder

Re: Apache Ignite 1.8 Release

[jira] [Created] (IGNITE-4296) Optimize GridDhtPartitionsSingleMessage processing

[jira] [Created] (IGNITE-4295) GridUnsafe: implement specialized methods for every kind of copy operation.

[jira] [Created] (IGNITE-4294) Allow unaligned memory access flag override in GridUnsafe.

21 matches

Site Navigation

Mail list logo

Footer information