Custom aggregate function in H2 SQL

[sibnick]

I need add my custom aggregate function to H2 SQL. Currently it is not
possible with Ignite API. I developed simple patch for this issue. Initially
I supposed that it is directly related to IGNITE-2177. But now I realized
that these issues are related but differ. Should I create new JIRA issue for
custom aggregate functions in H2 SQL or modify initial  IGNITE-2177 ?



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Custom-aggregate-function-in-H2-SQL-tp11254.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: New patch for Cassandra persistent store

[Alexey Kuznetsov]

Hi Igor!

I reviewed and merged to master.

Thanks for your contribution.

On Thu, Sep 15, 2016 at 6:08 AM, Igor Rudyak  wrote:

> Hi guys,
>
> Could somebody please look at the new pull request:
> https://github.com/apache/ignite/pull/1062
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[GitHub] ignite pull request #1062: IGNITE 3791 Wrap keyspace, table and column name ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1055: IGNITE-3421: Add ability to configure maxIterCnt ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1063: ignite-db-x-11386

[sboikov]

GitHub user sboikov opened a pull request:

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

ignite-db-x-11386



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

$ git pull https://github.com/gridgain/apache-ignite ignite-db-x-11386

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

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


commit 6dba3c5dad4eafb39fe3e9c27e21bd05a4085ef9
Author: dkarachentsev 
Date:   2016-07-07T14:37:32Z

GG-11276 - Overflow pages to save entries larger than page size.

commit 15175d4602a075c98f734d4f398612a31a23c212
Author: dkarachentsev 
Date:   2016-07-07T16:36:07Z

GG-11276 - Overflow pages to save entries larger than page size.

- Added remove.
- Fixes.

commit e4051a24d1a5779acc0de7d1ce83602dd6afaee4
Author: dkarachentsev 
Date:   2016-07-08T07:19:31Z

GG-11276 - Overflow pages to save entries larger than page size.

- Minors.

commit 8619701fff5dee4976a10e68ef064b0139449cc5
Author: dkarachentsev 
Date:   2016-07-08T08:19:48Z

GG-11276 - Overflow pages to save entries larger than page size.

- Set free spaze to 0 if no free items left.

commit 0640a8a2afca65457f4dca27cba025be6520
Author: dkarachentsev 
Date:   2016-07-08T09:21:09Z

Merge branch 'ignite-db-x' into ignite-gg-11196

commit d551655deab72100ce3290a6d051fa7ca630e086
Author: dkarachentsev 
Date:   2016-07-08T09:25:00Z

Merge branch 'ignite-db-x' into ignite-gg-11196

commit 902fc739a76c86de9703b4b2b141e55729fe35f5
Author: dkarachentsev 
Date:   2016-07-08T10:35:55Z

GG-11196 - Store metadata per cache.

Refactor.

commit 34abd348e1368e1ad4ae3a23c102a142de4ebe95
Author: dkarachentsev 
Date:   2016-07-08T12:51:00Z

GG-11196 - Store metadata per cache. Remove Meta space.

- Remove Meta space.

commit 0c132d0f3550f3c80c4599fe1ef45800ca69ba41
Author: ascherbakoff 
Date:   2016-06-21T05:25:56Z

IGNITE-3326 Map-reduce query waits for rebalancing forever when it's 
disabled. - Fixes #813.

Signed-off-by: Sergi Vladykin 

commit 41bbed1ff57544a39226e61106614a71cef34240
Author: Aleksei Scherbakov 
Date:   2016-07-08T15:14:37Z

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

commit 55751ddfefad64eb3d93dbfab50c89f17437ed2c
Author: Alexey Goncharuk 
Date:   2016-07-11T02:53:37Z

Merge ignite-db-x into ignite-gg-11276

commit b128a003f9c7a7cd7ac8594da6864d103216d0c5
Author: Alexey Goncharuk 
Date:   2016-07-11T02:54:55Z

Fixed compilation.

commit 3c8116c3d989e2386af674ffe0d72f0554ab8561
Author: dkarachentsev 
Date:   2016-07-11T06:49:03Z

Merge branch 'ignite-gg-11196' into ignite-gg-11220

# Conflicts:
#   
modules/indexing/src/test/java/org/apache/ignite/internal/processors/database/BPlusTreeSelfTest.java

commit 9b3bb34afddfad3da08fe963355d92f4e20eed42
Author: dkarachentsev 
Date:   2016-07-11T06:50:20Z

Merge branch 'ignite-gg-11196' into ignite-gg-11220

# Conflicts:
#   
modules/indexing/src/test/java/org/apache/ignite/internal/processors/database/BPlusTreeSelfTest.java

commit a2a6f04bbf4f9987239d5a9eee95e4917f69a448
Author: dkarachentsev 
Date:   2016-07-11T09:24:44Z

GG-11196 - Store metadata per cache. Remove Meta space.

commit 3a0c59012d1836b5657b7b43a941ddeea6b87a25
Author: dkarachentsev 
Date:   2016-07-11T09:25:29Z

GG-11220 - Cleanup metadata storage when cache/partition is destroyed.

commit 0f0047249de539bfff6cfb69c382ff153d653c05
Author: dkarachentsev 
Date:   2016-07-11T10:40:10Z

Merge branch 'ignite-gg-11196' into ignite-gg-11220

commit 427a7b1d642b95f3daeebfa90f800060ad29f69c
Author: dkarachentsev 
Date:   2016-07-11T12:30:45Z

GG-11220 - Cleanup metadata storage when cache/partition is destroyed.

commit eed7aca3dabf5bc8d899b7e79021d8af7f116ffc
Author: Sergi Vladykin 
Date:   2016-07-11T16:29:38Z

ignite-db-x - tree destroy

commit b024a1f018b419d413687f1deeed17ae4e0a19b5
Author: Sergi Vladykin 
Date:   2016-07-11T19:47:58Z

ignite-db-x - tree destroy2

commit 779c42a34d9953a478430f2346a5add077042cb4
Author: dkarachentsev 
Date:   2016-07-12T07:18:13Z

Merge branch 'ignite-db-x' into ignite-gg-11196

commit 74e78e4027fb1c5aeb0d9c95e131dfa32aacfe6b
Author: dkarachentsev 
Date:   2016-07-12T07:53:00Z

Merge branch 'ignite-gg-11196' into ignite-gg-11220

commit 6024564fd356b98b61520a018e7a2d2849268dba
Author: dkarachentsev 
Date:   2016-07-12T08:17:49Z

GG-11220 - Cleanup metadata storage when cache/partition is destroyed.

- Added usage of destroy()

commit c3d01f0b48f677a1e776b68409ed9229cf421397
Author: dkarachentsev 
Date:   2016-07-12T09:02:18Z

GG-11220 - Cleanup metadata storage when cache/partition is destroyed.

- Remove TODOs

commit b70630c3dff678f0dce892b19

New patch for Cassandra persistent store

[Igor Rudyak]

Hi guys,

Could somebody please look at the new pull request:
https://github.com/apache/ignite/pull/1062

[GitHub] ignite pull request #1062: IGNITE 3791 Wrap keyspace, table and column name ...

[irudyak]

Github user irudyak closed the pull request at:

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


---
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 #1062: IGNITE 3791 Wrap keyspace, table and column name ...

[irudyak]

GitHub user irudyak reopened a pull request:

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

IGNITE 3791 Wrap keyspace, table and column name with escape characters in 
generated CQL queries



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

$ git pull https://github.com/irudyak/ignite ignite-3791

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

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


commit f38a14defd0f1ebd41e0f49ef19f44902d1780d0
Author: Igor 
Date:   2016-09-14T23:01:11Z

printing index DDL statements if there are any indexes registered for a 
table

commit 27e551fe10a9577d63ebb9e6849aba1de1e5def3
Author: Igor 
Date:   2016-09-14T23:02:22Z

wrapped table name, keyspace name and column names with double quotes in 
all generated DDL/DML statements




---
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 #1062: Ignite 3791 Wrap keyspace, table and column name ...

[irudyak]

GitHub user irudyak opened a pull request:

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

Ignite 3791 Wrap keyspace, table and column name with escape characters in 
generated CQL queries



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

$ git pull https://github.com/irudyak/ignite ignite-3791

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

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


commit f38a14defd0f1ebd41e0f49ef19f44902d1780d0
Author: Igor 
Date:   2016-09-14T23:01:11Z

printing index DDL statements if there are any indexes registered for a 
table

commit 27e551fe10a9577d63ebb9e6849aba1de1e5def3
Author: Igor 
Date:   2016-09-14T23:02:22Z

wrapped table name, keyspace name and column names with double quotes in 
all generated DDL/DML statements




---
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 #172: IGNITE-1371 implemented

[irudyak]

Github user irudyak closed the pull request at:

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


---
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-3904) Add an option to serialize specific type(s) with OptimizedMarshaller when binary format is used

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-3904:
---

 Summary: Add an option to serialize specific type(s) with 
OptimizedMarshaller when binary format is used
 Key: IGNITE-3904
 URL: https://issues.apache.org/jira/browse/IGNITE-3904
 Project: Ignite
  Issue Type: Improvement
  Components: binary
Affects Versions: 1.7
Reporter: Valentin Kulichenko
Priority: Critical
 Fix For: 1.8


Currently binary marshaller delegates to optimized marshaller for 
{{Externalizable}} classes and classes that have {{write/readObject}} methods. 
It can be useful to manually force this behavior for other classes as well.

We can add {{BinaryTypeConfiguration.useOptimizedMarshaller}} property for this.



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

[jira] [Created] (IGNITE-3903) Throw an exception if @QuerySqlField annotation is attached to a method and binary marshaller is used

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-3903:
---

 Summary: Throw an exception if @QuerySqlField annotation is 
attached to a method and binary marshaller is used
 Key: IGNITE-3903
 URL: https://issues.apache.org/jira/browse/IGNITE-3903
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 1.7
Reporter: Valentin Kulichenko
 Fix For: 1.8


Currently query annotations attached to methods are processed even if binary 
marshaller is used. Since these methods are never called for binary objects, 
that leads to counterintuitive behavior. We should throw an exception on early 
stage in this case.



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

[jira] [Created] (IGNITE-3902) Hadoop: unreliable context classloader manipulations.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-3902:
---

 Summary: Hadoop: unreliable context classloader manipulations.
 Key: IGNITE-3902
 URL: https://issues.apache.org/jira/browse/IGNITE-3902
 Project: Ignite
  Issue Type: Bug
  Components: hadoop
Affects Versions: 1.7
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.8






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

Re: request for contributors permissions

[Denis Magda]

Hi,

I’ve granted you contributors permissions in JIRA. You’re ready to go.

—
Denis

> On Sep 13, 2016, at 6:34 PM, sibnick  wrote:
> 
> My JIRA profile for issues.apache.org:
> Username: sibnick
> Full Name:Tolstokulakov Nikolay
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-developers.2346864.n4.nabble.com/request-for-contributors-permissions-tp11198p11218.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Issue IGNITE-3850:need to add support WIN for YARN integration

[Denis Magda]

Hi,

What’s your JIRA account ID? I need to add you to the contributors list first 
and after that you’ll be able to assign it on yourself.

Also please get to know Apache Ignite’s contribution process
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 


—
Denis

> On Sep 14, 2016, at 8:37 AM, shirley feng  wrote:
> 
> hi,
> 
> I'm Shirely, I reported this issues on ignite user list(
> http://apache-ignite-users.70518.x6.nabble.com/why-allocated-containers-much-more-than-INGNITE-NODE-COUNT-td7226.html).
> Now I have figured it out and want to contribute to this issue. Would you
> please assign it to me?
> 
> Thanks
> Shirely

[GitHub] ignite pull request #1061: Fixed GridCacheStopSelfTest

[ilantukh]

GitHub user ilantukh opened a pull request:

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

Fixed GridCacheStopSelfTest



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

$ git pull https://github.com/ilantukh/ignite GridCacheStopSelfTest

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

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


commit 095def020f0106425b0cd8135a08ee2f994b053e
Author: Ilya Lantukh 
Date:   2016-09-14T15:48:41Z

Fixed GridCacheStopSelfTest.

commit 4734b190e205c7a04f185245619c8f4803a08d9f
Author: Ilya Lantukh 
Date:   2016-09-14T16:46:56Z

Merge branch 'master' of https://github.com/ilantukh/ignite into 
GridCacheStopSelfTest




---
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-3901) Mesos deployment: some Mesos parameters don't work correctly

[Vasilisa Sidorova (JIRA)]

Vasilisa  Sidorova created IGNITE-3901:
--

 Summary: Mesos deployment: some Mesos parameters don't work 
correctly
 Key: IGNITE-3901
 URL: https://issues.apache.org/jira/browse/IGNITE-3901
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.6
 Environment: Ubuntu 14.04, Apache Ignite 1.6.7
Reporter: Vasilisa  Sidorova


-
DESCRIPTION
-
Mesos deployment failed if IGNITE_PACKAGE_URL is used (instead IGNITE_VERSION 
or IGNITE_PACKAGE_PATH parameters)
-
STEPS FOR REPRODUCE
-
# Prepare marathon.json file for deployment  through Marathon and set correct 
IGNITE_PACKAGE_URL here
# Run framework according to instruction 
https://apacheignite.readme.io/docs/mesos-deployment
-
ACTUAL RESULT
-
Ignition application is started but nodes couldn't be running as binaries is 
not fully downloaded (look at the attached picture)
-
EXPECTED RESULT
-
Deployment is successful as for IGNITE_VERSION parameter
-
ADDITIONAL INFO
-
Reproducible for running framework via jar file in the default mode (without 
properties.prop file)



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

Issue IGNITE-3850:need to add support WIN for YARN integration

[shirley feng]

hi,

I'm Shirely, I reported this issues on ignite user list(
http://apache-ignite-users.70518.x6.nabble.com/why-allocated-containers-much-more-than-INGNITE-NODE-COUNT-td7226.html).
Now I have figured it out and want to contribute to this issue. Would you
please assign it to me?

Thanks
Shirely

[jira] [Created] (IGNITE-3900) Need to include yardstick-benchmarks to binary release

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-3900:
-

 Summary: Need to include yardstick-benchmarks to binary release
 Key: IGNITE-3900
 URL: https://issues.apache.org/jira/browse/IGNITE-3900
 Project: Ignite
  Issue Type: Sub-task
Reporter: Yakov Zhdanov


I think this should be included the same way as examples are - source code with 
all the necessary stuff to build, deploy, run and gather results.

This way user will be able to adapt benchmarks to certain deployments and 
easily run benchmarks.



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

[jira] [Created] (IGNITE-3899) Need to automate benchmark running and gathering results

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-3899:
-

 Summary: Need to automate benchmark running and gathering results
 Key: IGNITE-3899
 URL: https://issues.apache.org/jira/browse/IGNITE-3899
 Project: Ignite
  Issue Type: Sub-task
Reporter: Yakov Zhdanov


We need to think over on how to automate bench runs and gathering results.

I think this should be a script that handles
# build
## from local sources
## from git 
# deploy
## local network 
## Amazon EC2
# run - launching servers and drivers
# stopping and cleaning up
## Shutting down Amazon instances
# gathering all the results

This script (or set of scripts) should be implemented for Linux and Win

I would also expect the result to be easily adopted for running under TeamCity.



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

[GitHub] ignite pull request #1060: Ignite 3727 2

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

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

Ignite 3727 2



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

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

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

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


commit 4e6605f1691a43b2ba57da3d4eef98e6dd460a43
Author: DmitriyGovorukhin 
Date:   2016-08-30T15:38:13Z

IGNITE-3727: added ability intercept "stop listener" message, check future 
status after invoke stopRemoteListen.

commit bb899bdbb253ac51c2ee3cc89e51ec4ab6e88157
Author: DmitriyGovorukhin 
Date:   2016-08-31T13:43:34Z

IGNITE-613: particular solved problem, check all node for result

commit 1f31fdb47b7b0f8d621ee1c96927038591cd369d
Author: DmitriyGovorukhin 
Date:   2016-09-02T14:15:44Z

IGNITE-3727: added comment for message send method, details behavior

commit cf4cd05f9abdbeae096c6eb2d364dd140b06bbdc
Author: DmitriyGovorukhin 
Date:   2016-09-05T06:34:49Z

IGNITE-3727: update javadoc

commit 784958bf6e0e8e81191af498f6a993b2bfd78204
Author: DmitriyGovorukhin 
Date:   2016-09-06T16:35:14Z

IGNITE-1678  code + test+ benchmark config

commit 6485ae58c1f6dafdbfcf4de4f258f1386affa723
Author: DmitriyGovorukhin 
Date:   2016-09-08T11:55:09Z

IGNITE-2539 issues reproduce  test

commit ccae9b0673ff169be94cfc393dfbd43f4867ffa5
Author: DmitriyGovorukhin 
Date:   2016-09-08T11:57:25Z

IGNITE-2539 fix issue, move cleanup code

commit 7e6042420b804fffaed771767ba1f00e8bb5413d
Author: DmitriyGovorukhin 
Date:   2016-09-08T12:42:35Z

IGNITE-3727 send message, local listeners will execute through thread pool

commit ecd3d93e69e4ffaceec49052181ad7a80b321152
Author: DmitriyGovorukhin 
Date:   2016-09-08T16:08:32Z

IGNITE-2539 fix code version pre 1.8 now 1.7

commit a6980abbf5d8ff80ed8a83f479729ef418dfa7c9
Author: DmitriyGovorukhin 
Date:   2016-09-08T17:02:43Z

IGNITE-3727 supported sync/async execution for local listener

commit 271619d5d50aadd6f6de418725d81f53819953f2
Author: DmitriyGovorukhin 
Date:   2016-09-08T17:10:39Z

IGNITE-3727 license header

commit 14e1a6b300109e84bf1a0652673fa674a9ea83b3
Author: DmitriyGovorukhin 
Date:   2016-09-08T17:24:08Z

IGNITE-3727 start/stop async remote listener test

commit e3855a35b71a7f6e5bd96ab3b4572d11d049d6f7
Author: DmitriyGovorukhin 
Date:   2016-09-09T08:11:00Z

IGNITE-3727 send(..) javadoc update

commit e68a4fa2f25c9533dd38bbe25a6a98b804b5ca35
Author: DmitriyGovorukhin 
Date:   2016-09-09T08:17:41Z

IGNITE-3727 GridIO javadoc update

commit 8b416e8b2b3ea8f0a56eb9e41098df0b96a59cc9
Author: DmitriyGovorukhin 
Date:   2016-09-09T09:02:19Z

IGNITE-3727 test send sync/async and small fix in code

commit 190a5c99fae2fe16afea5a59ba5fd6ca6aef900c
Author: DmitriyGovorukhin 
Date:   2016-09-09T09:26:24Z

IGNITE-3727 update test, added 2 new cases

commit 9cdc754aaa367573dfc713230057e7094f678148
Author: sboikov 
Date:   2016-09-12T19:46:48Z

merge from master

commit e4b44a811e8d3145023252d76155deb286ed2d1c
Author: sboikov 
Date:   2016-09-12T20:23:07Z

ignite-3727 minor

commit 14cb9f5d3ea788f3cf4a96fe77c346c192173c5c
Author: DmitriyGovorukhin 
Date:   2016-09-13T09:57:59Z

IGNITE-3727 fix notes from jira.

commit 21e0093adf8978523e5c9451dd44f3087d65ca3d
Author: DmitriyGovorukhin 
Date:   2016-09-13T10:00:17Z

IGNITE-3727 fix notes from jira. (small update)

commit 980df4ea1be385867c69d2fa977f22d808701aca
Author: DmitriyGovorukhin 
Date:   2016-09-13T11:27:08Z

Revert "IGNITE-1678  code + test+ benchmark config"

This reverts commit 784958bf6e0e8e81191af498f6a993b2bfd78204.

commit 62f91abd32a261cd9c1aaa29dce930fe96a748a7
Author: DmitriyGovorukhin 
Date:   2016-09-13T11:39:17Z

Revert "IGNITE-2539 fix issue, move cleanup code"

This reverts commit ccae9b0673ff169be94cfc393dfbd43f4867ffa5.

commit a1f0db9d5d3e63940f158cb30cfaf3d51f558630
Author: DmitriyGovorukhin 
Date:   2016-09-13T11:42:03Z

Revert  "IGNITE-2539 issues reproduce test"

commit 60b030cdf27dfa6567630f3157e5e370a08834c1
Author: DmitriyGovorukhin 
Date:   2016-09-13T12:43:37Z

IGNITE-3727 fix test

commit de59444b235ae325bb35976dbd0f211ce8dfb69c
Author: DmitriyGovorukhin 
Date:   2016-09-14T08:18:10Z

ignite-3727  added test for sendOrdered + javadoc (behavior sendOrdered)

commit c9ed5c6583e803110a34fc0126ae4e5af56331b1
Author: DmitriyGovorukhin 
Date:   2016-09-14T09:58:20Z

ignite-3727  added test for multi-thread sendOrdered




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

[jira] [Created] (IGNITE-3898) Add more information for Debugging

[hahadada (JIRA)]

hahadada created IGNITE-3898:


 Summary: Add more information for Debugging
 Key: IGNITE-3898
 URL: https://issues.apache.org/jira/browse/IGNITE-3898
 Project: Ignite
  Issue Type: Improvement
  Components: clients
Affects Versions: 1.6
Reporter: hahadada


Hi,

We see following error in our grid quite frequently.


2016-09-09 09:36:12.458 BST [WARN] -
thread="tcp-disco-msg-worker-#2%%" -
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi" - Timed out
waiting for message to be read (most probably, the reason is in long GC
pauses on remote node) [curTimeout=2]

What is missing in this are the details about remote node (id/host/port).

I believe if it is trying to connect and timeout, then it also knows which node 
that is) those details so that one can go and instantly check memory status. 
For larger grid, checking logs and memory status for each remote node is 
difficult.

Can we please add node details along with user attributes for remote node in 
same log message. This way it will be easier to identify which remote node 
caused issue in a large grid.

As to details, default nodeid/hostname/port shall suffice, however, it would 
still be less obvious to identify nodes.

Can we add a flag -DPrintTheseUserAttributesAboutRemoteNode=""(apologies for very simple name)
or -DPrintAlluserAttributesAboutRemoteNode. This way one can identify nodes 
more cleanly in same log message.

Thanks.


Thanks.



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

[GitHub] ignite pull request #1059: IGNITE-3897 Test transactional behaviour of cache...

[leveyj]

GitHub user leveyj opened a pull request:

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

IGNITE-3897 Test transactional behaviour of caches during rolling restart

This submission includes 2 new tests for the IgniteCacheFailoverTestSuite 
that validate the results of an aggregation function running against a cluster 
undergoing rolling restart.

Also, the following supporting Assertions are included:
(1) EventualAssertion - based on the Assertion interface added in 
IGNITE-3678, this assertion has a timeout and retests the assertion with 
exponential back-off until successful, or failure.
(2) CacheNodeSafeAssertion - an assertion to make the rolling restart of 
nodes deterministic, in that it ensures that the primary and backup partitions 
are distributed such that no data is lost.

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

$ git pull https://github.com/leveyj/ignite IGNITE-3897

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

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


commit 4e6b623b7adb66ea917573835ba4b298b65ad501
Author: John Levey 
Date:   2016-08-03T10:32:22Z

IGNITE-3897 Test transactional behaviour of caches during rolling restart




---
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-3897) Test transactional behaviour of caches during rolling restart

[John Levey (JIRA)]

John Levey created IGNITE-3897:
--

 Summary: Test transactional behaviour of caches during rolling 
restart
 Key: IGNITE-3897
 URL: https://issues.apache.org/jira/browse/IGNITE-3897
 Project: Ignite
  Issue Type: Test
  Components: cache
Affects Versions: 1.7
Reporter: John Levey
Assignee: John Levey


Create a test that validates the following conditions against a running cluster 
that is undergoing a rolling restart:
* Validate a continuous aggregate sum against the cluster during restarts
* Validate transaction handling against the cluster during restarts

See also https://issues.apache.org/jira/browse/IGNITE-3456



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

[GitHub] ignite pull request #1045: ignite-db-x-free1

[sboikov]

Github user sboikov closed the pull request at:

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


---
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 #1051: IGNITE-3868: Fix for driver installiation.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1021: ignite-1.6.7

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1035: IGNITE-3831: Added distributed query to example.

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1023: IGNITE-3613 IGFS: IgfsImpl.size() doesn't take se...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3896) Cache POJO store with Percona and the MariaDB shoud correctry select dialect

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-3896:
-

 Summary: Cache POJO store with Percona and the MariaDB shoud 
correctry select dialect
 Key: IGNITE-3896
 URL: https://issues.apache.org/jira/browse/IGNITE-3896
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.8
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko






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

[jira] [Created] (IGNITE-3895) Web console: Should split large generated XML and Java files.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-3895:
-

 Summary: Web console: Should split large generated XML and Java 
files.
 Key: IGNITE-3895
 URL: https://issues.apache.org/jira/browse/IGNITE-3895
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Reporter: Vasiliy Sisko






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

Re: request for contributors permissions

[sibnick]

Now I successfully subscribed  to dev mail list



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/request-for-contributors-permissions-tp11198p11223.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.