Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

There's update for DML testing and binary package:

IGNITE-4321 Cassandra modules

IGNITE-4323 DML: INSERT INTO SELECT .. FROM statement causes
IgniteException: Wrong value has been set


On Mon, Nov 28, 2016 at 11:15 AM, Alexey Kuznetsov 
wrote:

> Vladimir,
>
> IGNITE-3443 Implement collecting what SQL statements executed on cluster
> and their metrics.
>
> --
> Alexey Kuznetsov
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

Re: Talking to Ignite From PHP

[Igor Sapego]

Denis,

yes.

Best Regards,
Igor

On Mon, Nov 28, 2016 at 8:26 PM, Denis Magda  wrote:

> Igor,
>
> Has everything been merged into 1.8? Can I start checking PHP/PDO guide?
>
> —
> Denis
>
> > On Nov 11, 2016, at 3:52 AM, Igor Sapego  wrote:
> >
> > Denis,
> >
> > I'm ready to merge it as soon as the 1.8 branch is ready. Once it ready
> I'm
> > and DML is merged to it, I'm going to merge 1.8 to my branch. After that
> I
> > believe there is going to be some kind of testing from my side and review
> > from the community side and then I'll merge it to 1.8 once my
> contribution
> > is accepted. I believe everything from my side is not going to take more
> than
> > few hours, so it all depends on when 1.8 branch is ready and how long
> review
> > is going to take.
> >
> >
> > Best Regards,
> > Igor
> >
> > On Thu, Nov 10, 2016 at 11:06 PM, Denis Magda  > wrote:
> > Igor,
> >
> > I didn’t manage to merge the branches. There were conflicts that I
> couldn’t resolve properly on my side.
> >
> > Please let me know once everything gets merged into 1.8 branch so that I
> can go through the guide from the beginning till the end. Do you think it
> can be done by next Monday?
> >
> > In the meanwhile, I do like the documentation in its present state and
> left a couple of minor comments in the related ticket
> > https://issues.apache.org/jira/browse/IGNITE-3921 <
> https://issues.apache.org/jira/browse/IGNITE-3921>
> >
> > —
> > Denis
> >
> >> On Nov 3, 2016, at 5:46 AM, Igor Sapego > wrote:
> >>
> >> Denis,
> >>
> >> It seems like someone have deleted branch ignite-3910 or maybe I just
> forgot to push it
> >> to remote repository. However, I've pushed it now. Check it please.
> >>
> >> Thanks for your contribution to the documentation and pointing out what
> can be further
> >> improved. I'm already working on it.
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Thu, Nov 3, 2016 at 1:51 AM, Denis Magda  > wrote:
> >> Igor,
> >>
> >> I can’t find branch ignite-3910. Most likely you keep the changes on
> the other one. Please double check.
> >>
> >> In any case, I succeeded with some of the steps from the documentation
> and updated it making clearer.
> >> http://apacheignite.gridgain.org/v1.7/docs/pdo-interoperability <
> http://apacheignite.gridgain.org/v1.7/docs/pdo-interoperability>
> >>
> >> Please apply my latest notes related to the documentation.
> >> https://issues.apache.org/jira/browse/IGNITE-3921 <
> https://issues.apache.org/jira/browse/IGNITE-3921>
> >>
> >> Let me know as soon as the documentation is refined. I’ll keep at the
> installation and testing of PHP + Ignite scenario.
> >>
> >> —
> >> Denis
> >>
> >>> On Nov 2, 2016, at 4:38 AM, Igor Sapego > wrote:
> >>>
> >>> Denis,
> >>>
> >>> I believe that you should switch to DML branch (ignite-2294),
> >>> and then merge ignite-3910 into it.
> >>>
> >>> That should be enough. Please let me know if there are any issues.
> >>>
> >>> Best Regards,
> >>> Igor
> >>>
> >>> On Wed, Nov 2, 2016 at 3:12 AM, Denis Magda  > wrote:
> >>> Igor,
> >>>
> >>> I’m planning to prepare a blog post about our PHP + PDO + Ignite
> integration and referring to the documentation template available for now
> >>> https://apacheignite.readme.io/docs/pdo-interoperability <
> https://apacheignite.readme.io/docs/pdo-interoperability>
> >>>
> >>> Considering that the fixes and improvements you did for Ignite ODBC
> driver in order to support PDO have not been released yet what is a valid
> branch number if I want to do the following:
> >>> - connect to the cluster from PHP code.
> >>> - populate a cache using DML INSERT command.
> >>> - query the data with the usage of SQL.
> >>>
> >>> —
> >>> Denis
> >>>
> >>>
> >>
> >>
> >
> >
>
>

[jira] [Created] (IGNITE-4325) Proposing new marshaller mapping should be done in synchronous way

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-4325:
---

 Summary: Proposing new marshaller mapping should be done in 
synchronous way
 Key: IGNITE-4325
 URL: https://issues.apache.org/jira/browse/IGNITE-4325
 Project: Ignite
  Issue Type: Sub-task
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov


h3. Notes
Previous version of DiscoveryCustomEvent-based MarshallerContext implementation 
returned immediately with "not registered" flag after submitting request for 
new mapping.
This may be ineffective in terms of network traffic and not well suited with 
current implementation of BinaryCache.

h3. Acceptance Criteria
# Registration of new mapping should return when the mapping is accepted by 
grid.
# Registration of new mapping should throw an exception when the mapping is in 
conflict with grid.



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

Re: Talking to Ignite From PHP

[Denis Magda]

Igor,

Has everything been merged into 1.8? Can I start checking PHP/PDO guide?

—
Denis

> On Nov 11, 2016, at 3:52 AM, Igor Sapego  wrote:
> 
> Denis,
> 
> I'm ready to merge it as soon as the 1.8 branch is ready. Once it ready I'm
> and DML is merged to it, I'm going to merge 1.8 to my branch. After that I
> believe there is going to be some kind of testing from my side and review
> from the community side and then I'll merge it to 1.8 once my contribution
> is accepted. I believe everything from my side is not going to take more than
> few hours, so it all depends on when 1.8 branch is ready and how long review
> is going to take.
> 
> 
> Best Regards,
> Igor
> 
> On Thu, Nov 10, 2016 at 11:06 PM, Denis Magda  > wrote:
> Igor,
> 
> I didn’t manage to merge the branches. There were conflicts that I couldn’t 
> resolve properly on my side.
> 
> Please let me know once everything gets merged into 1.8 branch so that I can 
> go through the guide from the beginning till the end. Do you think it can be 
> done by next Monday?
> 
> In the meanwhile, I do like the documentation in its present state and left a 
> couple of minor comments in the related ticket
> https://issues.apache.org/jira/browse/IGNITE-3921 
> 
> 
> —
> Denis
> 
>> On Nov 3, 2016, at 5:46 AM, Igor Sapego > > wrote:
>> 
>> Denis,
>> 
>> It seems like someone have deleted branch ignite-3910 or maybe I just forgot 
>> to push it
>> to remote repository. However, I've pushed it now. Check it please.
>> 
>> Thanks for your contribution to the documentation and pointing out what can 
>> be further
>> improved. I'm already working on it.
>> 
>> Best Regards,
>> Igor
>> 
>> On Thu, Nov 3, 2016 at 1:51 AM, Denis Magda > > wrote:
>> Igor,
>> 
>> I can’t find branch ignite-3910. Most likely you keep the changes on the 
>> other one. Please double check.
>> 
>> In any case, I succeeded with some of the steps from the documentation and 
>> updated it making clearer.
>> http://apacheignite.gridgain.org/v1.7/docs/pdo-interoperability 
>> 
>> 
>> Please apply my latest notes related to the documentation.
>> https://issues.apache.org/jira/browse/IGNITE-3921 
>> 
>> 
>> Let me know as soon as the documentation is refined. I’ll keep at the 
>> installation and testing of PHP + Ignite scenario.
>> 
>> —
>> Denis
>> 
>>> On Nov 2, 2016, at 4:38 AM, Igor Sapego >> > wrote:
>>> 
>>> Denis,
>>> 
>>> I believe that you should switch to DML branch (ignite-2294),
>>> and then merge ignite-3910 into it.
>>> 
>>> That should be enough. Please let me know if there are any issues.
>>> 
>>> Best Regards,
>>> Igor
>>> 
>>> On Wed, Nov 2, 2016 at 3:12 AM, Denis Magda >> > wrote:
>>> Igor,
>>> 
>>> I’m planning to prepare a blog post about our PHP + PDO + Ignite 
>>> integration and referring to the documentation template available for now
>>> https://apacheignite.readme.io/docs/pdo-interoperability 
>>> 
>>> 
>>> Considering that the fixes and improvements you did for Ignite ODBC driver 
>>> in order to support PDO have not been released yet what is a valid branch 
>>> number if I want to do the following:
>>> - connect to the cluster from PHP code.
>>> - populate a cache using DML INSERT command.
>>> - query the data with the usage of SQL.
>>> 
>>> —
>>> Denis
>>> 
>>> 
>> 
>> 
> 
> 

[GitHub] ignite pull request #1298: IGNITE-3886 .NET: Build script

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-3886 .NET: Build script



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

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

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

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


commit 6b8942d305a24bc97f64414d6e863fc757a829d5
Author: Pavel Tupitsyn 
Date:   2016-11-28T13:39:31Z

IGNITE-3886 .NET: Build script

commit 37bfc70b5f0dd3dedd4c00599d8b08865e5c9002
Author: Pavel Tupitsyn 
Date:   2016-11-28T13:53:43Z

Merge branch 'master' into ignite-3886

commit 504c61c7bdfdcd99669851c65b6030551dec9174
Author: Pavel Tupitsyn 
Date:   2016-11-28T13:58:26Z

wip

commit 22f20325fad53b41f97f453ed5acf5784ef253a7
Author: Pavel Tupitsyn 
Date:   2016-11-28T13:59:29Z

wip

commit 271ac6e0d9efd8bd109cf3f62cc2f276928fa2ab
Author: Pavel Tupitsyn 
Date:   2016-11-28T14:56:07Z

wip build Java

commit bb3da08955eb87748ba74aea0b9a689472b1dedf
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:16:00Z

wip

commit dd4cd97631fb1d28cfd82022a221db037669699e
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:17:17Z

wip

commit 231761d274db4a6366ad32c3397666d4c027
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:22:55Z

wip

commit e76dd6c412de7c195bff82ada6f09395d8aa02ac
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:30:44Z

Java and .NET build steps done

commit 8cfb5870e3181e8af800960ee3ec546bcf732f49
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:33:33Z

wip

commit 35a581b34f96f78fb87a02a8acde9d02fc432ddc
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:34:10Z

wip

commit e144548beabd96d9dc243bf0516efcebfaf23605
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:44:13Z

wip

commit a03eadd92b33f9977173ec7ac47db58af7441efd
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:51:13Z

Fix quotes

commit 94b926d2f3f3c2f7c72f7cdacaebac0040016b67
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:52:53Z

Add gitignore

commit 1262d13e2c6fdaea5171eb06ff34faa92a2811ec
Author: Pavel Tupitsyn 
Date:   2016-11-28T15:57:57Z

wip code analysis

commit b3ae02859b1424373a8cdecb13ff38a93313bb0e
Author: Pavel Tupitsyn 
Date:   2016-11-28T16:33:04Z

Add batch file for easy run

commit bf787254932fbfd905060e0756356d8d647e0f2b
Author: Pavel Tupitsyn 
Date:   2016-11-28T16:50:52Z

NuGet packaging added

commit 0600f548928bf6f9ecbb0ac5b594a3e2fff5bb60
Author: Pavel Tupitsyn 
Date:   2016-11-28T16:54:03Z

minors




---
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 #1297: IGNITE-4247: Sql queries supports table alias.

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-4247: Sql queries supports table alias.

Big fixed.

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

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

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

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


commit 029bbee10b415d49dd765ca4b1377dac137ab2c7
Author: Andrey V. Mashenkov 
Date:   2016-11-28T14:27:33Z

Sql queries supports table alias.




---
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 #1287: IGNITE-3169 .NET: Provide error messages for inco...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1296: IGNITE-4140

[adasari]

GitHub user adasari opened a pull request:

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

IGNITE-4140

KafkaDataStreamer - added new kafka streamer which uses the extractor.

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

$ git pull https://github.com/adasari/ignite IGNITE-4140

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

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


commit 15168221f38327aca89dfd7160fe473434526463
Author: unknown 
Date:   2016-11-28T12:29:10Z

StreamAdapter - added empty check to avoid exception
KafkaDataStreamer - added new kafka streamer which uses the extractor.




---
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 #1295: StreamAdapter - added empty check to avoid except...

[adasari]

Github user adasari closed the pull request at:

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


---
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 #1295: StreamAdapter - added empty check to avoid except...

[adasari]

GitHub user adasari opened a pull request:

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

StreamAdapter - added empty check to avoid exception

KafkaDataStreamer - added new kafka streamer which uses the extractor.

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

$ git pull https://github.com/adasari/ignite IGNITE-4140

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

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


commit 15168221f38327aca89dfd7160fe473434526463
Author: unknown 
Date:   2016-11-28T12:29:10Z

StreamAdapter - added empty check to avoid exception
KafkaDataStreamer - added new kafka streamer which uses the extractor.




---
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-4323) DML: INSERT INTO SELECT .. FROM statement causes IgniteException: Wrong value has been set

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4323:
-

 Summary: DML: INSERT INTO SELECT .. FROM statement causes 
IgniteException: Wrong value has been set
 Key: IGNITE-4323
 URL: https://issues.apache.org/jira/browse/IGNITE-4323
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


The idea of scenario to copy data from cache to cache.

0. Extract the attachment into {{examples}} directory
1. Start {{org.apache.ignite.examples.datagrid.ExtSqlExampleNodeStartup}}
2. Start one ore more {{org.apache.ignite.examples.datagrid.ExtSqlExample}}
{noformat}
Exception in thread "main" javax.cache.CacheException: class 
org.apache.ignite.IgniteException: Wrong value has been set 
[typeName=org.apache.ignite.testtools.model.AllTypes, fieldName=enumCol, 
fieldType=Enum, assignedValueType=Object]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
at 
org.apache.ignite.examples.datagrid.ExtSqlExample.main(ExtSqlExample.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class org.apache.ignite.IgniteException: Wrong value has been set 
[typeName=org.apache.ignite.testtools.model.AllTypes, fieldName=enumCol, 
fieldType=Enum, assignedValueType=Object]
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:817)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
... 6 more
Caused by: class org.apache.ignite.IgniteCheckedException: Wrong value has been 
set [typeName=org.apache.ignite.testtools.model.AllTypes, fieldName=enumCol, 
fieldType=Enum, assignedValueType=Object]
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1800)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:810)
... 7 more
Caused by: class org.apache.ignite.binary.BinaryObjectException: Wrong value 
has been set [typeName=org.apache.ignite.testtools.model.AllTypes, 
fieldName=enumCol, fieldType=Enum, assignedValueType=Object]
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.checkMetadata(BinaryObjectBuilderImpl.java:418)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.serializeTo(BinaryObjectBuilderImpl.java:227)
at 
org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl.build(BinaryObjectBuilderImpl.java:187)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.rowToKeyValue(DmlStatementsProcessor.java:809)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.doInsert(DmlStatementsProcessor.java:705)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:282)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:155)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:185)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:812)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:810)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1777)
... 8 more
{noformat}



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

[GitHub] ignite pull request #1294: IGNITE-4263 Hadoop: abstract out offheap/heap mem...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-4263  Hadoop: abstract out offheap/heap memory management.



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

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

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

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


commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 517deeb718d91ad5727504c48228106e283b76c2
Author: tledkov-gridgain 
Date:   2016-11-25T16:27:27Z

IGNITE-4263: save the progress

commit ea2f6b0ffcfa723742ade762051ce39d13f24837
Author: tledkov-gridgain 
Date:   2016-11-28T10:49:06Z

IGNITE-4263: fix HeapMemeoryManager, add test

commit 9f5ea4391270d09d5e4bf2d64f6ae2ff58e9a91a
Author: tledkov-gridgain 
Date:   2016-11-28T10:50:39Z

IGNITE-4263: revert base test




---
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: Code Reviews with Upsource

[Anton Vinogradov]

It works,
Thanks!

On Mon, Nov 28, 2016 at 1:40 PM, Pavel Tupitsyn 
wrote:

> Igniters,
>
> Upsource code review tool licensing is sorted out and we can start using
> it:
> http://reviews.ignite.apache.org/ignite/view
>
> Brief instructions:
> https://cwiki.apache.org/confluence/display/IGNITE/How+
> to+Contribute#HowtoContribute-ReviewWithUpsource
>
> Let me know if you have any questions.
>
> Pavel
>

[GitHub] ignite pull request #1293: IGNITE-4017 DML example.

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-4017 DML example.



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

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

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

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


commit 62a9afe06ef2e6b2e65097c79c4ebc24a3c67166
Author: Alexander Paschenko 
Date:   2016-11-28T10:08:26Z

IGNITE-4017 DML example.




---
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.
---

Code Reviews with Upsource

[Pavel Tupitsyn]

Igniters,

Upsource code review tool licensing is sorted out and we can start using it:
http://reviews.ignite.apache.org/ignite/view

Brief instructions:
https://cwiki.apache.org/confluence/display/IGNITE/How+
to+Contribute#HowtoContribute-ReviewWithUpsource

Let me know if you have any questions.

Pavel

[jira] [Created] (IGNITE-4322) .NET: ClientReconnectExample is not clear enough

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-4322:
---

 Summary: .NET: ClientReconnectExample is not clear enough 
 Key: IGNITE-4322
 URL: https://issues.apache.org/jira/browse/IGNITE-4322
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Ksenia Rybakova


ClientReconnectExample has the following output

{noformat}
>>> Client reconnect example started.
[13:19:53]__  
[13:19:53]   /  _/ ___/ |/ /  _/_  __/ __/
[13:19:53]  _/ // (7 7// /  / / / _/
[13:19:53] /___/\___/_/|_/___/ /_/ /___/
[13:19:53]
[13:19:53] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
[13:19:53] 2016 Copyright(C) Apache Software Foundation
[13:19:53]
[13:19:53] Ignite documentation: http://ignite.apache.org
[13:19:53]
[13:19:53] Quiet mode.
[13:19:53]   ^-- Logging to file 
'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
[13:19:53]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[13:19:53]
[13:19:53] OS: Windows 10 10.0 amd64
[13:19:53] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
[13:19:53] Initial heap size is 256MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[13:19:53] Configured plugins:
[13:19:53]   ^-- None
[13:19:53]
[13:19:58] Security status [authentication=off, tls/ssl=off]
[13:19:59] Performance suggestions for grid 'serverNode' (fix if possible)
[13:19:59] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[13:19:59]   ^-- Disable grid events (remove 'includeEventTypes' from 
configuration)
[13:19:59]   ^-- Disable fully synchronous writes (set 
'writeSynchronizationMode' to PRIMARY_SYNC or FULL_ASYNC)
[13:19:59]
[13:19:59] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[13:19:59]
[13:19:59] Ignite node started OK (id=a18708d8, grid=serverNode)
[13:19:59] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
>>> Server node started.
[13:20:00]__  
[13:20:00]   /  _/ ___/ |/ /  _/_  __/ __/
[13:20:00]  _/ // (7 7// /  / / / _/
[13:20:00] /___/\___/_/|_/___/ /_/ /___/
[13:20:00]
[13:20:00] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
[13:20:00] 2016 Copyright(C) Apache Software Foundation
[13:20:00]
[13:20:00] Ignite documentation: http://ignite.apache.org
[13:20:00]
[13:20:00] Quiet mode.
[13:20:00]   ^-- Logging to file 
'C:\WORK\Releases\apache-ignite-fabric-1.8.0-QASK2501-bin\work\log\ignite-a18708d8.0.log'
[13:20:00]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[13:20:00]
[13:20:00] OS: Windows 10 10.0 amd64
[13:20:00] VM information: Java(TM) SE Runtime Environment 1.8.0_91-b14 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14
[13:20:00] Initial heap size is 256MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[13:20:00] Configured plugins:
[13:20:00]   ^-- None
[13:20:00]
[13:20:00] Security status [authentication=off, tls/ssl=off]
[13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
[13:20:02] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[13:20:02]
[13:20:02] Ignite node started OK (id=2f5922f5)
[13:20:02] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=3.5GB]
>>> Client node connected to the cluster.
>>> Put value with key:0
>>> Put value with key:1
>>> Put value with key:2
[13:20:04,824][SEVERE][tcp-client-disco-sock-writer-#5%null%][TcpDiscoverySpi] 
Failed to send message: TcpDiscoveryClientPingRequest 
[nodeToPing=a18708d8-e489-4b47-a8e9-e16efc6b814e, 
super=TcpDiscoveryAbstractMessage [sndNodeId=null, 
id=a9fa27aa851-2f5922f5-d38b-4b4f-80cf-feec8bf52013, verifierNodeId=null, 
topVer=0, pendingIdx=0, failedNodes=null, isClient=false]]
java.net.SocketException: Socket is closed
at java.net.Socket.getOutputStream(Socket.java:943)
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.writeToSocket(TcpDiscoverySpi.java:1354)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1088)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
[13:20:04] Ignite node stopped OK [name=serverNode, uptime=00:00:04:899]
>>> Put value with key:3
[13:20:09] New version is available at ignite.apache.org: 1.7.0
>>> Restarting server node...
[13:20:09]__  
[13:20:09]   /  _/ ___/ |/ /  _/_  __/ __/
[13:20:09]  _/ // (7 7// /  / / / _/
[13:20:09] /___/\___/_/|_/___/ /_/ /___/
[13:20:09]
[13:20:09] ver. 1.8.0-QASK2501#20161125-sha1:ccbe6007
[13:20:09] 2016 Copyright(C) Apache Software Foundation
[13:20:09]
[13:20:09] Ignite documentation: http://ignite.apache.org
[13:20:09]
[13:20:09] Quiet mode.
[13:20:09]   ^-- Logging to file 

[jira] [Created] (IGNITE-4321) Cassandra modules

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4321:
-

 Summary: Cassandra modules
 Key: IGNITE-4321
 URL: https://issues.apache.org/jira/browse/IGNITE-4321
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


Binary fabric edition now has following modules:
{noformat}
 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:13   964 README.txt
   1 файлов964 байт

 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-serializers

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:1353 231 asm-5.0.3.jar
25.11.2016  22:1312 181 
ignite-cassandra-serializers-1.8.0-QASK2502.jar
25.11.2016  22:13   285 211 kryo-3.0.3.jar
25.11.2016  22:13  licenses
25.11.2016  22:13 5 711 minlog-1.3.0.jar
25.11.2016  22:1341 755 objenesis-2.1.jar
25.11.2016  22:13 1 345 README.txt
25.11.2016  22:1320 738 reflectasm-1.10.1.jar
   7 файлов420 172 байт

 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-serializers\licenses

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:1311 358 apache-2.0.txt
25.11.2016  22:13 1 857 ignite-cassandra-serializers-licenses.txt
   2 файлов 13 215 байт

 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-store

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:13   990 392 cassandra-driver-core-3.0.0.jar
25.11.2016  22:13   232 019 commons-beanutils-1.8.3.jar
25.11.2016  22:13 2 308 517 guava-19.0.jar
25.11.2016  22:1391 897 ignite-cassandra-store-1.8.0-QASK2502.jar
25.11.2016  22:13  licenses
25.11.2016  22:1385 448 metrics-core-3.0.2.jar
25.11.2016  22:13   196 881 netty-buffer-4.0.33.Final.jar
25.11.2016  22:13   145 779 netty-codec-4.0.33.Final.jar
25.11.2016  22:13   441 447 netty-common-4.0.33.Final.jar
25.11.2016  22:13   272 139 netty-handler-4.0.33.Final.jar
25.11.2016  22:13   349 164 netty-transport-4.0.33.Final.jar
25.11.2016  22:13 1 228 README.txt
  11 файлов  5 114 911 байт

 Содержимое папки 
C:\Work\apache-ignite-fabric-1.8.0-QASK2502-bin\libs\optional\ignite-cassandra-store\licenses

25.11.2016  22:13  .
25.11.2016  22:13  ..
25.11.2016  22:1311 358 apache-2.0.txt
25.11.2016  22:13   294 ignite-cassandra-store-licenses.txt
   2 файлов 11 652 байт

{noformat}

I suppose that {{ignite-cassandra}} directory must be removed and rest of 
Cassandra modules should be joined into one.



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

[GitHub] ignite pull request #1292: IGNITE-4320 Minor fixes inside DML engine

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-4320 Minor fixes inside DML engine



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

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

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

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


commit 78313af8699130b0f6dee16bd5c969224e640a8b
Author: Alexander Paschenko 
Date:   2016-11-27T17:52:50Z

IGNITE-4320 Minor fixes inside DML engine




---
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-4320) Minor fixes in DmlStatementsProcessor

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4320:
---

 Summary: Minor fixes in DmlStatementsProcessor
 Key: IGNITE-4320
 URL: https://issues.apache.org/jira/browse/IGNITE-4320
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.8
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko


1. Important local variable renamed to more sane name
2. Removed duplicate operation manipulations in doUpdate
3. Small optimization in doUpdate (don't read key fields as we won't use them 
anyway)



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

[GitHub] ignite pull request #1291: IGNITE-4319 Test fix

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-4319 Test fix



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

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

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

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






---
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-4319) Fix IgniteCacheAbstractSqlDmlQuerySelfTest

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4319:
---

 Summary: Fix IgniteCacheAbstractSqlDmlQuerySelfTest
 Key: IGNITE-4319
 URL: https://issues.apache.org/jira/browse/IGNITE-4319
 Project: Ignite
  Issue Type: Test
Reporter: Alexander Paschenko


Somehow it's green on TC in non binary mode but fails locally. Purely test 
problem.



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

[jira] [Created] (IGNITE-4318) GridNioEmbeddedFuture and GridEmbeddedFuture have different interface and behaviour.

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-4318:


 Summary: GridNioEmbeddedFuture and GridEmbeddedFuture have 
different interface and behaviour.
 Key: IGNITE-4318
 URL: https://issues.apache.org/jira/browse/IGNITE-4318
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Denis Kholodov


{{GridNioEmbeddedFuture}} should be put in line with {{GridEmbeddedFuture}}. 
Tests should look similar.



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

Re: Apache Ignite 1.8 Release

[Alexey Kuznetsov]

Vladimir,

IGNITE-3443 Implement collecting what SQL statements executed on cluster
and their metrics.

-- 
Alexey Kuznetsov

[jira] [Created] (IGNITE-4317) Redesign Queries Screen

[Dmitriy Shabalin (JIRA)]

Dmitriy Shabalin created IGNITE-4317:


 Summary: Redesign Queries Screen
 Key: IGNITE-4317
 URL: https://issues.apache.org/jira/browse/IGNITE-4317
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Shabalin
Assignee: Dmitriy Shabalin


Simplify queries screen to implement divide execute action and sql action



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

[GitHub] ignite pull request #1290: Ignite 4312

[alexpaschenko]

Github user alexpaschenko closed the pull request at:

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


---
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-4316) visorcmd: batch mode works incorrect in some case

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-4316:
--

 Summary: visorcmd: batch mode works incorrect in some case
 Key: IGNITE-4316
 URL: https://issues.apache.org/jira/browse/IGNITE-4316
 Project: Ignite
  Issue Type: Bug
  Components: visor
Affects Versions: 1.8
Reporter: Pavel Konstantinov
 Fix For: 1.9


I've faced with incorrect working in case of such run:
"ignitevisorcmd -np -e=open;1;top;node;0"

I'm expected the following execution of this command:
1) open connection with config file by number 1 in the list
2) execute 'top'
3) execute 'node' command selected node number 0

But really visor executed 'open'   with default config (config with number 0) 
and do not use node number in command 'node;0'

Another issue if I set commands inside quotes "open;1;top;node;0"
In this case visor prints "Input string is too long".



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