Re: TeamCity: dead builds

[Petr Ivanov]

Point 1 - Done.

Point 2 - I hope some other community members will arise to comment on how to 
proceed with this build - either remove this project or revive it in 
perspective of our to-java-9 movement and necessity to check project 
compatibility on all available JDKs.



> On 8 Dec 2017, at 00:00, Dmitry Pavlov  wrote:
> 
> Hi Petr,
> 
> About point 1
> https://ci.ignite.apache.org/admin/editDependencies.html?id=buildType:IgniteTests_RunAll
>  
> 
> :
> if you see in UI message like following
> «build configuration with ID
> "IgniteTests_IgniteIndexedObjectsCacheExpiryPolicy" does not exist»
> this means there is no such build. Feel free to remove.
> 
> I'm not sure abount point 2.
> 
> Sincerely,
> Dmitriy Pavlov
> 
> чт, 7 дек. 2017 г. в 19:27, Petr Ivanov  >:
> 
>> Hi, all.
>> 
>> 
>> Found several issues in TeamCity concerning dead (started last time long
>> time ago) build and snapshot dependencies:
>> * Ignite Tests [1]
>>* -> Run All
>>   * Ignite_IgniteJms
>>   * Ignite_IgniteMqtt
>>   * IgniteTests_IgniteCacheFullApiPortable
>>   * IgniteTests_IgniteCachePortabl
>>   * IgniteTests_IgniteCacheQueryPortable
>>   * IgniteTests_IgniteIndexedObjectsCache
>>   * IgniteTests_IgniteIndexedObjectsCache2
>>   * IgniteTests_IgniteIndexedObjectsCache3
>>   * IgniteTests_IgniteIndexedObjectsCache4
>>   * IgniteTests_IgniteIndexedObjectsCacheExpiryPolicy
>>   * IgniteTests_IgniteIndexedObjectsCacheFailover
>>   * IgniteTests_IgniteIndexedObjectsCacheFailover2
>>   * IgniteTests_IgniteIndexedObjectsCacheFullApi
>>   * IgniteTests_IgniteIndexedObjectsCacheRestarts
>>   * IgniteTests_IgniteIndexedObjectsDataStrucutures
>>   * IgniteTests_IgniteIndexedObjectsQueries
>> * Ignite JDK compatibility [2]: all builds (started last time about 22
>> month ago)
>> 
>> Request approve on snapshot dependency cleanup and dead builds removal.
>> 
>> 
>> [1] -
>> https://ci.ignite.apache.org/admin/editDependencies.html?id=buildType:IgniteTests_RunAll
>> <
>> https://ci.ignite.apache.org/admin/editDependencies.html?id=buildType:IgniteTests_RunAll
>>  
>> 
>>> 
>> [2] -
>> https://ci.ignite.apache.org/project.html?projectId=IgniteJdkCompatibility 
>> 
>> <
>> https://ci.ignite.apache.org/project.html?projectId=IgniteJdkCompatibility 
>> 

[GitHub] ignite pull request #3177: IGNITE-7145 Fixed print of warning message.

[vsisko]

GitHub user vsisko opened a pull request:

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

IGNITE-7145 Fixed print of warning message.



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

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

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

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


commit 6be9a94c82884e7fd8620795281fcb8cc4b05600
Author: vsisko 
Date:   2017-12-08T03:32:48Z

IGNITE-7145 Fixed print of warning message.




---

Re: Apache Ignite as a distributed processing back-ends

[Romain Manni-Bucau]

Hi

This sounds awesome to have an Ignite runner which could compete with
hazelcast-jet.

The entry point would be https://beam.apache.org/contribute/runner-guide/
IMHO.

Being on Ignite cluster also opens a lot of doors - reusing the filesystem
or distributed structures. Very exiting.

Le 8 déc. 2017 05:46, "Denis Magda"  a écrit :

> Hello Apache Beam fellows!
>
> We at Apache Ignite community came across your project and would be happy
> to integrate with it.
>
> In short, Ignite is a distributed database and computational platform that
> has its own map-reduce like component:
> https://apacheignite.readme.io/docs/compute-grid
>
> The integration will give Beam users an ability to use Ignite as a
> distributed processing back-end system and database.
>
> How should we proceed? Please share any relevant information.
>
> —
> Denis
> Ignite PMC
>

Apache Ignite as a distributed processing back-ends

[Denis Magda]

Hello Apache Beam fellows!

We at Apache Ignite community came across your project and would be happy to 
integrate with it. 

In short, Ignite is a distributed database and computational platform that has 
its own map-reduce like component:
https://apacheignite.readme.io/docs/compute-grid 


The integration will give Beam users an ability to use Ignite as a distributed 
processing back-end system and database.

How should we proceed? Please share any relevant information.

—
Denis
Ignite PMC

[jira] [Created] (IGNITE-7146) Assertion in GridCacheTxFinishSync

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-7146:


 Summary: Assertion in GridCacheTxFinishSync
 Key: IGNITE-7146
 URL: https://issues.apache.org/jira/browse/IGNITE-7146
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Alexander Belyak


Got assertion error in clear log:
{noformat}
2017-12-07 17:24:10.358 
[ERROR][sys-#2376%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.GridClosureProcessor] 
Closure execution failed with error.

java.lang.AssertionError: null
at 
org.apache.ignite.internal.processors.cache.distributed.GridCacheTxFinishSync$TxFinishSync.onSend(GridCacheTxFinishSync.java:250)
at 
org.apache.ignite.internal.processors.cache.distributed.GridCacheTxFinishSync$ThreadFinishSync.onSend(GridCacheTxFinishSync.java:163)
at 
org.apache.ignite.internal.processors.cache.distributed.GridCacheTxFinishSync.onFinishSend(GridCacheTxFinishSync.java:70)
at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.beforeFinishRemote(IgniteTxManager.java:1522)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:750)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:690)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:430)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.rollbackNearTxLocalAsync(GridNearTxLocal.java:3314)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.access$4900(GridNearTxLocal.java:122)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$26.run(GridNearTxLocal.java:4130)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6685)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2017-12-07 17:24:10.358 
[ERROR][sys-#2376%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.GridClosureProcessor] 
Runtime error caught during grid runnable execution: GridWorker 
[name=closure-proc-worker, igniteInstanceName=DPL_GRID%DplGridNodeName, 
finished=false, hashCode=1220995949, interrupted=false, 
runner=sys-#2376%DPL_GRID%DplGridNodeName%]
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7145) Visor CMD: Fix tests for: Ignite Visor Console

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7145:
-

 Summary: Visor CMD: Fix tests for: Ignite Visor Console
 Key: IGNITE-7145
 URL: https://issues.apache.org/jira/browse/IGNITE-7145
 Project: Ignite
  Issue Type: Test
Reporter: Vasiliy Sisko
Assignee: Vasiliy Sisko


https://ci.ignite.apache.org/viewLog.html?buildId=984720=buildResultsDiv=Ignite20Tests_IgniteVisorConsoleTestDetach



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: IGNITE-7107 Apache Ignite RPM packages

[Dmitriy Setrakyan]

Thanks Petr, this is awesome. To be honest, I can hardly wait until it will
be possible to install Ignite with yum or apt-get.

D.

On Thu, Dec 7, 2017 at 7:02 AM, Petr Ivanov  wrote:

> HI, all!
>
>
> Within the task IGNITE-7107 I’ve prepare pull request #3171 [1] with:
>  - specification to build RPM package out of built binary archive;
>  - corresponding instruction in DEVNOTES.txt
>
> Also took responsibility to introduced style correction and unification to
> DEVNOTES.txt
>
>
> [1] - https://github.com/apache/ignite/pull/3171

Re: TeamCity: dead builds

[Dmitry Pavlov]

Hi Petr,

About point 1
https://ci.ignite.apache.org/admin/editDependencies.html?id=buildType:IgniteTests_RunAll
:
if you see in UI message like following
«build configuration with ID
"IgniteTests_IgniteIndexedObjectsCacheExpiryPolicy" does not exist»
this means there is no such build. Feel free to remove.

I'm not sure abount point 2.

Sincerely,
Dmitriy Pavlov

чт, 7 дек. 2017 г. в 19:27, Petr Ivanov :

> Hi, all.
>
>
> Found several issues in TeamCity concerning dead (started last time long
> time ago) build and snapshot dependencies:
>  * Ignite Tests [1]
> * -> Run All
>* Ignite_IgniteJms
>* Ignite_IgniteMqtt
>* IgniteTests_IgniteCacheFullApiPortable
>* IgniteTests_IgniteCachePortabl
>* IgniteTests_IgniteCacheQueryPortable
>* IgniteTests_IgniteIndexedObjectsCache
>* IgniteTests_IgniteIndexedObjectsCache2
>* IgniteTests_IgniteIndexedObjectsCache3
>* IgniteTests_IgniteIndexedObjectsCache4
>* IgniteTests_IgniteIndexedObjectsCacheExpiryPolicy
>* IgniteTests_IgniteIndexedObjectsCacheFailover
>* IgniteTests_IgniteIndexedObjectsCacheFailover2
>* IgniteTests_IgniteIndexedObjectsCacheFullApi
>* IgniteTests_IgniteIndexedObjectsCacheRestarts
>* IgniteTests_IgniteIndexedObjectsDataStrucutures
>* IgniteTests_IgniteIndexedObjectsQueries
>  * Ignite JDK compatibility [2]: all builds (started last time about 22
> month ago)
>
> Request approve on snapshot dependency cleanup and dead builds removal.
>
>
> [1] -
> https://ci.ignite.apache.org/admin/editDependencies.html?id=buildType:IgniteTests_RunAll
> <
> https://ci.ignite.apache.org/admin/editDependencies.html?id=buildType:IgniteTests_RunAll
> >
> [2] -
> https://ci.ignite.apache.org/project.html?projectId=IgniteJdkCompatibility
> <
> https://ci.ignite.apache.org/project.html?projectId=IgniteJdkCompatibility
> >
>
>

[GitHub] ignite pull request #3173: IGNITE-6373 Create example for local and distribu...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3176: IGNITE-7113 Processing of redundant type names

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-7113 Processing of redundant type names



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

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

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

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


commit 071d55881db33cadcda40b568978bca3a151d8b3
Author: Alexander Paschenko 
Date:   2017-12-07T17:11:11Z

IGNITE-7113 Processing of redundant type names




---

[GitHub] ignite pull request #3175: ignite-6827-asch

[ascherbakoff]

GitHub user ascherbakoff opened a pull request:

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

ignite-6827-asch

Test changes related to tx rollback on topology change.

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

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

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

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


commit 99a05f50be24a6dbebe6e9a3cd57513a1dbeb4fb
Author: Aleksei Scherbakov 
Date:   2017-12-06T11:26:44Z

IGNITE-6827 wip.

commit 1e7ee0f0fd10e21b36cc57e1499358dd46c616b7
Author: Aleksei Scherbakov 
Date:   2017-12-06T14:34:25Z

IGNITE-6827 wip.

commit 0b0c0ff5f736b6cb299bf8ee32d6705d3c2adfb2
Author: Aleksei Scherbakov 
Date:   2017-12-06T14:47:13Z

IGNITE-6827 wip.

commit 2e7e7a2eca9b45ca1488403d86c28df055d215a7
Author: Aleksei Scherbakov 
Date:   2017-12-06T15:01:37Z

IGNITE-6827 wip.

commit 50dbdb8f14751f470f605884f195256531f4176f
Author: Aleksei Scherbakov 
Date:   2017-12-06T15:04:40Z

IGNITE-6827 wip.

commit 4da15f51af7302dc70fa5ee705042dec36cb120b
Author: Aleksei Scherbakov 
Date:   2017-12-06T16:46:22Z

IGNITE-6827 wip.

commit bc024837e12627a011c8a1b43f30783bb3b08f2d
Author: Aleksei Scherbakov 
Date:   2017-12-06T17:11:04Z

IGNITE-6827 wip.

commit 8f5693361b018ee78ca7b6fd9a9e4d88017a87ea
Author: ascherbakoff 
Date:   2017-12-06T21:05:42Z

IGNITE-6827 wip.

commit c4b9fab158769fb21e7dbbb641746868698a6652
Author: Aleksei Scherbakov 
Date:   2017-12-07T11:23:25Z

IGNITE-6827 wip.

commit f0a6113798df0e20e2d3b4a5573a5c722a2fd948
Author: Aleksei Scherbakov 
Date:   2017-12-07T11:27:16Z

IGNITE-6827 wip.

commit 5d9d22c7cb27c39516d0340ab72fa0a4f56e004b
Author: Aleksei Scherbakov 
Date:   2017-12-07T11:46:21Z

IGNITE-6827 wip.

commit a008c220923d95155285b3408945f6e2c94104e5
Author: Aleksei Scherbakov 
Date:   2017-12-07T13:47:40Z

IGNITE-6827 wip.

commit f0ba7bd90ab16f0933353901fd73586e998443ba
Author: Aleksei Scherbakov 
Date:   2017-12-07T14:05:14Z

IGNITE-6827 wip.




---

[GitHub] ignite pull request #3174: IGNITE-7110: Javadoc package descriptions missed ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3174: IGNITE-7110: Javadoc package descriptions missed ...

[ybabak]

GitHub user ybabak opened a pull request:

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

IGNITE-7110: Javadoc package descriptions missed for ML

fixed.

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

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

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

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


commit 3e48a703208b99451f0191746cc20f9ec7809d13
Author: YuriBabak 
Date:   2017-12-07T16:27:39Z

IGNITE-7110: Javadoc package descriptions missed for ML

fixed.




---

[GitHub] ignite pull request #3173: IGNITE-6373 Create example for local and distribu...

[oignatenko]

GitHub user oignatenko opened a pull request:

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

IGNITE-6373 Create example for local and distributed k-means algorithm

- examples implemented
-- verified with diffs overview, clean build and execution of examples

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

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

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

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


commit b0cc9d74dfd664f3be11cadb0a43369819b3e8b5
Author: Oleg Ignatenko 
Date:   2017-12-07T15:56:14Z

IGNITE-6373 Create example for local and distributed k-means algorithm
- examples implemented
-- verified with diffs overview, clean build and execution of examples




---

[GitHub] ignite pull request #3069: Ignite 6872 1

[oignatenko]

Github user oignatenko closed the pull request at:

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


---

[GitHub] ignite pull request #3168: IGNITE-6872 Linear regression should implement Mo...

[asfgit]

Github user asfgit closed the pull request at:

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


---

IGNITE-7144 Java 9: fix build issue with tools.jar not found

[Petr Ivanov]

Hi, all.


Within the task IGNITE-7144 I’ve prepare pull request #3172 [1] with changes to 
maven build instructions to overcome project compilation not starting on java-9 
because of missing tools.jar lib.


[1] - https://github.com/apache/ignite/pull/3172 

[GitHub] ignite pull request #3172: IGNITE-7144 Java 9: fix build issue with tools.ja...

[vveider]

GitHub user vveider opened a pull request:

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

IGNITE-7144 Java 9: fix build issue with tools.jar not found

 * added profiles to parent and ignite-tools modules to detect java-9 
environment and run parametrised build
 * added macOS compatibility for previouse java versions

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

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

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

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


commit fedf126db357ba04cda08cdec2c709101140ff4c
Author: Ivanov Petr 
Date:   2017-12-07T15:07:59Z

IGNITE-7144 Java 9: fix build issue with tools.jar not found
 * added profiles to parent and ignite-tools modules to detect java-9 
environment and run parametrised build
 * added macOS compatibility for previouse java versions




---

[jira] [Created] (IGNITE-7144) Java 9: fix build issue with tools.jar not found

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7144:


 Summary: Java 9: fix build issue with tools.jar not found
 Key: IGNITE-7144
 URL: https://issues.apache.org/jira/browse/IGNITE-7144
 Project: Ignite
  Issue Type: Improvement
Reporter: Peter Ivanov
Assignee: Peter Ivanov


{code}
[ERROR] Failed to execute goal on project ignite-tools: Could not resolve 
dependencies for project org.apache.ignite:ignite-tools:jar:2.4.0-SNAPSHOT: 
Could not find artifact com.sun:tools:jar:9.0.1 at specified path 
/Library/Java/JavaVirtualMachines/jdk-9.0.1.jdk/Contents/Home/../lib/tools.jar
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

IGNITE-7107 Apache Ignite RPM packages

[Petr Ivanov]

HI, all!


Within the task IGNITE-7107 I’ve prepare pull request #3171 [1] with:
 - specification to build RPM package out of built binary archive;
 - corresponding instruction in DEVNOTES.txt

Also took responsibility to introduced style correction and unification to 
DEVNOTES.txt


[1] - https://github.com/apache/ignite/pull/3171

[jira] [Created] (IGNITE-7143) CPP: Can not insert zero decimal value with the ODBC driver.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-7143:
---

 Summary: CPP: Can not insert zero decimal value with the ODBC 
driver.
 Key: IGNITE-7143
 URL: https://issues.apache.org/jira/browse/IGNITE-7143
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Affects Versions: 2.1
Reporter: Igor Sapego


Create the following table:
{code}
CREATE TABLE IF NOT EXISTS TestTable (RecId varchar PRIMARY KEY, RecValue 
DECIMAL(4,2))
WITH "template=replicated, cache_name=TestTable_Cache";
{code}

Then do an ODBC insert using the OdbcParameter with the OdbcCommand object:

{code}
INSERT INTO TestTable (RecId, RecValue) VALUES ('1', ?)
{code}

The Odbc error is "The connection has been disabled." however the JVM is
throwing this error:

{noformat}
[SEVERE][client-connector-#47][ClientListenerNioListener] Failed to parse
client request.
java.lang.ArrayIndexOutOfBoundsException: 0
 at org.apache.ignite.internal.binary.BinaryUtils.doReadDecimal
{noformat}

Everything works out ok until the actual value set on the parameter is 0.
Null works fine, values other than 0 work fine. Precision and
Scale are set appropriately. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3171: IGNITE-7107 Apache Ignite RPM packages

[vveider]

GitHub user vveider opened a pull request:

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

IGNITE-7107 Apache Ignite RPM packages

 * added spec for RPM build
 * added instructions to DEVNOTES.txt

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

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

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

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


commit d902499bf9d1b25fc071a1f5e87f40b51c49edcd
Author: Peter Ivanov 
Date:   2017-12-06T17:28:52Z

IGNITE-7107 Apache Ignite RPM packages
 * added spec for RPM build
 * added instructions to DEVNOTES.txt




---

IGNITE-7142 Introduce ability to run Ignite Tests on TeamCity with Java 9

[Petr Ivanov]

Hi, all!


I’ve introduced ability to run Ignite Tests / Run All task in java-9 (and 
java-1.8 as well) environment configuration.
Detailed description: [1]. Please, be advised.


[1] 
https://issues.apache.org/jira/browse/IGNITE-7142?focusedCommentId=16281942=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16281942

[GitHub] ignite pull request #3170: Ignite 2.4.1 merge master fix lost partition

[DmitriyGovorukhin]

GitHub user DmitriyGovorukhin opened a pull request:

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

Ignite 2.4.1 merge master fix lost partition



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-2.4.1-merge-master-fix-lost-partition

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

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


commit e7ca9b65a68de7752195c8f4d2b5180f3c77d19f
Author: Dmitriy Govorukhin 
Date:   2017-11-13T18:52:47Z

ignite-blt-merge -> ignite-2.4.1

commit cc8168fc184bb7f5e3cc3bbb0743397097f78bfb
Author: Dmitriy Govorukhin 
Date:   2017-11-13T19:13:01Z

merge ignite-pitr-rc1 -> ignite-2.4.1

commit 87e6d74cf6a251c7984f9e68c391f790feccc281
Author: Dmitriy Govorukhin 
Date:   2017-11-14T12:49:33Z

ignite-gg-12877 Compact consistent ID in WAL

commit 9f5a22711baea05bd37ab07c8f928a4837dd83a4
Author: Ilya Lantukh 
Date:   2017-11-14T14:12:28Z

Fixed javadoc.

commit d5af2d78dd8eef8eca8ac5391d31d8c779649bb0
Author: Alexey Kuznetsov 
Date:   2017-11-15T08:09:00Z

IGNITE-6913 Baseline: Added new options to controls.sh for baseline 
manipulations.

commit 713924ce865752b6e99b03bd624136541cea5f9f
Author: Sergey Chugunov 
Date:   2017-11-15T09:03:12Z

IGNITE-5850 failover tests for cache operations during BaselineTopology 
changes

commit b65fd134e748d496f732ec2aa0953a0531f544b8
Author: Ilya Lantukh 
Date:   2017-11-15T12:54:35Z

TX read logging if PITR is enabled.

commit 9b2a567c0e04dc33116b51f88bee75f76e9107d1
Author: Ilya Lantukh 
Date:   2017-11-15T13:45:16Z

TX read logging if PITR is enabled.

commit 993058ccf0b2b8d9e80750c3e45a9ffa31d85dfa
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:51:54Z

ignite-2.4.1 optimization for store full set node more compacted

commit 1eba521f608d39967aec376b397b7fc800234e54
Author: Dmitriy Govorukhin 
Date:   2017-11-15T13:52:22Z

Merge remote-tracking branch 'professional/ignite-2.4.1' into ignite-2.4.1

commit 564b3fd51f8a7d1d81cb6874df66d0270623049c
Author: Sergey Chugunov 
Date:   2017-11-15T14:00:51Z

IGNITE-5850 fixed issue with initialization of data regions on node 
activation, fixed issue with auto-activation when random node joins inactive 
cluster with existing BLT

commit c6d1fa4da7adfadc80abdc7eaf6452b86a4f6aa4
Author: Sergey Chugunov 
Date:   2017-11-15T16:23:08Z

IGNITE-5850 transitionResult is set earlier when request for changing 
BaselineTopology is sent

commit d65674363163e38a4c5fdd73d1c8d8e1c7610797
Author: Sergey Chugunov 
Date:   2017-11-16T11:59:07Z

IGNITE-5850 new failover tests for changing BaselineTopology up (new node 
added to topology)

commit 20552f3851fe8825191b144179be032965e0b5c6
Author: Sergey Chugunov 
Date:   2017-11-16T12:53:43Z

IGNITE-5850 improved error message when online node is removed from baseline

commit 108bbcae4505ac904a6db774643ad600bfb42c21
Author: Sergey Chugunov 
Date:   2017-11-16T13:45:52Z

IGNITE-5850 BaselineTopology should not change on cluster deactivation

commit deb641ad3bdbf260fa60ad6bf607629652e324bd
Author: Dmitriy Govorukhin 
Date:   2017-11-17T09:45:44Z

ignite-2.4.1 truncate wal and checkpoint history on move/delete snapshot

commit 3c8b06f3659af30d1fd148ccc0f40e216a56c998
Author: Alexey Goncharuk 
Date:   2017-11-17T12:48:12Z

IGNITE-6947 Abandon remap after single map if future is done (fixes NPE)

commit ba2047e5ae7d271a677e0c418375d82d78c4023e
Author: devozerov 
Date:   2017-11-14T12:26:31Z

IGNITE-6901: Fixed assertion during 
IgniteH2Indexing.rebuildIndexesFromHash. This closes #3027.

commit abfc0466d6d61d87255d0fe38cbdf11ad46d4f89
Author: Sergey Chugunov 
Date:   2017-11-17T13:40:57Z

IGNITE-5850 tests for queries in presence of BaselineTopology

commit f4eabaf2a905abacc4c60c01d3ca04f6ca9ec188
Author: Sergey Chugunov 
Date:   2017-11-17T17:23:02Z

IGNITE-5850 implementation for setBaselineTopology(long topVer) migrated 
from wc-251

commit 4edeccd3e0b671aa277f58995df9ff9935baa95a
Author: EdShangGG 
Date:   2017-11-17T18:21:17Z

GG-13074 Multiple snapshot test failures after baseline topology is 
introduced
-adding baseline test to suite
-fixing issues with baseline

Re: Ignite in docker (Native Persistence)

[Denis Magda]

Nick,

Excellent, here is a ticket! Please reassign it on me once you complete with 
the doc:
https://issues.apache.org/jira/browse/IGNITE-7132

—
Denis

> On Dec 7, 2017, at 3:57 AM, Nikolai Tikhonov  wrote:
> 
> Hello!
> 
> Yes, sure! I'll investigate this question and update our doc.
> 
> On Thu, Dec 7, 2017 at 9:57 AM, Denis Magda  > wrote:
> Nick,
> 
> As one of Ignite docker maintainers, could you please investigate one how to 
> map Ignite persistence to docker volumes:
> https://docs.docker.com/engine/admin/volumes/volumes/#use-a-read-only-volume 
> 
> 
> and update the docker documentation:
> https://apacheignite.readme.io/docs/docker-deployment 
> 
> 
> —
> Denis
> 
>> On Dec 1, 2017, at 8:40 AM, afedotov > > wrote:
>> 
>> Hi,
>> 
>> You need to create volumes and map them to the ${IGNITE_HOME}/work/db or any
>> other path that
>> you might have specified via setPersistentStorePath. These volumes should
>> outlive the Ignite containers
>> and thus it will be possible to reuse them on restart.
>> 
>> It's worth trying docker-compose, docker-swarm or kubernetes, depending on
>> your needs.
>> For example, Kubernetes provides a wide variety of volume options
>> https://kubernetes.io/docs/concepts/storage/volumes/ 
>> 
>> 
>> 
> Has anyone use Ignite Native Persistence with Docker? 
> Is there a solution on how to map the Volume dynamically? And how about when
> you restart the whole cluster, how does it maps all volumes?
>> 
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 
>> 
> 
> 

[jira] [Created] (IGNITE-7141) JDBC Driver 2.3.0 Incorrectly reads PK column meta data

[Josh (JIRA)]

Josh created IGNITE-7141:


 Summary: JDBC Driver 2.3.0 Incorrectly reads PK column meta data
 Key: IGNITE-7141
 URL: https://issues.apache.org/jira/browse/IGNITE-7141
 Project: Ignite
  Issue Type: Bug
  Components: jdbc
Affects Versions: 2.3
Reporter: Josh


It appears the meta data coming back while trying to read PK information about 
a table through the jdbc driver has two properties flipped (PK_NAME and 
COLUMN_NAME). 

I have a table with a PK column named ID and while querying the meta data 
through the driver I receive the following entries:

PK_NAME=ID
COLUMN_NAME=_KEY

I verified the same shows through a jdbc tool like Squirrel sql.





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7140) Error in cardinality checks in AbstractMatrix in methods plus and minus

[Artem Malykh (JIRA)]

Artem Malykh created IGNITE-7140:


 Summary: Error in cardinality checks in AbstractMatrix in methods 
plus and minus
 Key: IGNITE-7140
 URL: https://issues.apache.org/jira/browse/IGNITE-7140
 Project: Ignite
  Issue Type: Bug
Reporter: Artem Malykh
Assignee: Artem Malykh


Cardinality checks in mentioned methods compare matrix dimensions with its own 
dimensions instead of operands dimensions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Time and scope for Apache Ignite 2.4

[Andrey Gura]

Hi,

I've just updated the issue. Please take a look.

On Wed, Dec 6, 2017 at 6:44 AM, Dmitriy Setrakyan  wrote:
> On Tue, Dec 5, 2017 at 7:13 AM, Andrey Gura  wrote:
>
>> Hi,
>>
>> I'm working on WAL optimizations that improve performance
>> significantly [1]. I believe it's important task and should be
>> included in Apache Ignite 2.4 release.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-6339
>>
>>
> Andrey, I do not believe that moving WAL processing to a separate thread
> would provide a huge performance boost. Is there anything else you are
> doing? If yes, can you please describe it in the ticket?

[GitHub] ignite pull request #3136: IGNITE-7088 Fix implementation of DIRECT comparat...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3169: IGNITE-4192

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-4192



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

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

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

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


commit f6e982540e65ab17d439dba990794f35616a30dd
Author: sboikov 
Date:   2017-08-30T09:45:40Z

ignite-3478

commit 275a85db5cd6923b36126166ae99b15e876192be
Author: sboikov 
Date:   2017-08-31T07:44:07Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

commit b7b9089f0102b8cab9942a9c887d93e9f26cc7d2
Author: sboikov 
Date:   2017-08-31T09:00:36Z

disco cache cleanup

commit 855c2d45794c300d41e386b4e6fa40736cc3e40d
Author: sboikov 
Date:   2017-08-31T09:09:58Z

Merge branch 'ignite-3478-1' into ignite-3478

commit 08be7310a93d3ce455215b97cf8ab1a2c3f0ab31
Author: sboikov 
Date:   2017-08-31T09:52:23Z

ignite-3478

commit fce2e31f0fd2f4f6a9944422e40408a0c65cfe90
Author: sboikov 
Date:   2017-09-04T08:13:50Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

commit d3c049952384750c5543a9f88b383c033ef74096
Author: sboikov 
Date:   2017-09-04T08:52:11Z

ignite-3478

commit e71ce1937a18dd32448e92b1038dc48d4cb6f8ab
Author: sboikov 
Date:   2017-09-04T10:16:03Z

ignite-3478

commit 5fac5b0965e97f8951e16e10ca9229a2e78ddb0c
Author: sboikov 
Date:   2017-09-05T10:16:44Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

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

commit 2e0c9c08e046e8d6af1b5358d9053eae999b1fb4
Author: sboikov 
Date:   2017-09-05T11:30:55Z

ignite-3478

commit e1e07ffdf2d711ba3e72f316f5a3970eff27372e
Author: sboikov 
Date:   2017-09-05T11:31:14Z

ignite-3478

commit cbada3934a386668da0b11d4de7d0f58a4d04dfe
Author: sboikov 
Date:   2017-09-05T11:49:49Z

ignite-3484

commit 5a82c68dcd1927bb6fded8b7def38c91ff6e145b
Author: sboikov 
Date:   2017-09-05T11:59:49Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

commit bc9134c94b7a738dc1664e96ca6eabb059f1c268
Author: sboikov 
Date:   2017-09-05T12:03:39Z

Merge branch 'ignite-3478' into ignite-3484

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/tree/AbstractDataInnerIO.java

commit b4bfcde78825c6517232e49d389bdb5de19f05a9
Author: sboikov 
Date:   2017-09-05T12:27:51Z

ignite-3484

commit 43834aaab9e2c3cd5fdd55289fdc4a9ff8ab6599
Author: sboikov 
Date:   2017-09-05T13:13:00Z

ignite-3478

commit d1b828095713fcadfa260cf94fef01b42a1b12fd
Author: sboikov 
Date:   2017-09-05T13:13:33Z

Merge branch 'ignite-3478' into ignite-3484

commit 6be6779b6336c36cd71eef0a25199a6a877ce6b5
Author: sboikov 
Date:   2017-09-05T13:47:11Z

ignite-3484

commit e3bba83256c1eb53c4b40fbd9ddba47fcf9d58d5
Author: sboikov 
Date:   2017-09-06T07:10:26Z

ignite-3484

commit dd0afb28466094b801506da8afa3601bfaebd853
Author: sboikov 
Date:   2017-09-06T07:30:04Z

ignite-3484

commit 27b87b413348b03986a463551db24b7726321732
Author: sboikov 
Date:   2017-09-06T08:19:18Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

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

commit dcaf8801accd6ee089849a82b2ccd558aec81895
Author: sboikov 
Date:   2017-09-06T08:19:30Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-3478

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

commit c966451d0bf7059575de92bcfae43d72096ebce4
Author: sboikov 
Date:   2017-09-06T08:27:04Z

Merge branch 'ignite-3478' into ignite-3484

commit 91b9911731a387a3199ddbbc22704bc14af09995
Author: sboikov 
Date:   2017-09-06T09:22:22Z

ignite-3484

commit e40b4d9dcd6fe6c1cd2640bdd7116ca5a08ed781
Author: sboikov 
Date:   2017-09-07T09:12:32Z

ignite-3484

commit 41a1c571e6ba1765941e2f1679dc4ac1582275c4

[jira] [Created] (IGNITE-7139) SQL: Implement a lazy execution for the local queries.

[Roman Kondakov (JIRA)]

Roman Kondakov created IGNITE-7139:
--

 Summary: SQL: Implement a lazy execution for the local queries.
 Key: IGNITE-7139
 URL: https://issues.apache.org/jira/browse/IGNITE-7139
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Affects Versions: 2.3
Reporter: Roman Kondakov
 Fix For: 2.4


At the moment a lazy execution is implemented for the distributed queries only 
(see {{GridMapQueryExecutor}}). We need to add this feature for the local 
queries too.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7138) BinaryMetadata should be marshalled with standard JdkMarshaller instead of BinaryMarshaller

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-7138:
---

 Summary: BinaryMetadata should be marshalled with standard 
JdkMarshaller instead of BinaryMarshaller
 Key: IGNITE-7138
 URL: https://issues.apache.org/jira/browse/IGNITE-7138
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Chugunov
 Fix For: 3.0


When running in persistent-enabled mode each Ignite node writes all updates of 
BinaryMetadata to local file system right from discovery thread.

On writing metadata has to be marshalled into byte array, BinaryMarshaller is 
used at the moment (see BinaryMetadataFileStore class for implementation).
It turned out it can cause a deadlock (more details are in linked ticket) when 
BinaryMarshaller decides to register metadata for one of the fields of initial 
BinaryMetadata object.

JdkMarshaller should be used instead as it doesn't rely on internal mechanics 
of Ignite node.
As it breaks compatibility this change cannot be implemented in 2.x version.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3168: IGNITE-6872 Linear regression should implement Mo...

[oignatenko]

GitHub user oignatenko opened a pull request:

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

IGNITE-6872 Linear regression should implement Model API

Model and Trainer API implemented for OLS regression

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

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

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

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


commit cf6ba40c97840a28ee14f49f09f79fe3d9d5a66f
Author: Oleg Ignatenko 
Date:   2017-11-20T11:53:46Z

IGNITE-6872 Linear regression should implement Model API
- regression examples moved to more appropriate package
-- verified with diffs overview, clean build and execution of unit tests

commit a8dadee71e0ca2a00387cfa2dba9c656de75137f
Author: Oleg Ignatenko 
Date:   2017-11-20T11:57:18Z

IGNITE-6872 Linear regression should implement Model API
- added missing package-info
-- verified with diffs overview

commit cc8edfbd0ca7e20655f45dc82d576f2d21627497
Author: Oleg Ignatenko 
Date:   2017-11-20T14:12:03Z

IGNITE-6872 Linear regression should implement Model API
- implementation, tests and examples
- accommodated changes done to OLS per IGNITE-5846
- fixed some issues with coding style and javadoc
-- verified with diffs overview, clean build, execution of unit tests and 
examples

commit a0f294740b78dbe354a67a1658c9877544e587ea
Author: Oleg Ignatenko 
Date:   2017-11-21T08:57:27Z

IGNITE-6872 Linear regression should implement Model API
- decision trees example moved to more appropriate package
-- verified with diffs overview

commit e944568849d09f2bc7fca932bc043304208ff55d
Author: Oleg Ignatenko 
Date:   2017-11-21T13:25:31Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit dfa4ea896d404b7bd231b57e880b5745b9db634f
Author: Oleg Ignatenko 
Date:   2017-11-21T13:37:47Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit fe79868659d9a04d73234d800b7e5b1ba9029eeb
Author: Oleg Ignatenko 
Date:   2017-11-21T13:38:19Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit c69583b91eef73616827cbfe03ad9eb1ff7ccde0
Author: Oleg Ignatenko 
Date:   2017-11-21T13:42:56Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit 1ca1fb030d5be32843fce9746aa7d026a81d4502
Author: Oleg Ignatenko 
Date:   2017-11-21T13:45:15Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit 35918b024bca13dea3a061f623f743ab33f14cd7
Author: Oleg Ignatenko 
Date:   2017-11-21T13:49:53Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview, clean build, execution of unit tests and 
examples

commit 88fe344b83b9c9272eddc1c6e536febb0f8eff43
Author: Oleg Ignatenko 
Date:   2017-11-23T14:50:47Z

IGNITE-6872 Linear regression should implement Model API
- OLS regression Trainer wip - preliminary cleanup of QR decomposition
-- verified with diffs overview, clean build, execution of unit tests and 
examples

commit 24a27d9976fe5c1cf3ab876e410b4af63aec8792
Author: Oleg Ignatenko 
Date:   2017-11-23T15:26:20Z

IGNITE-6872 Linear regression should implement Model API
- OLS regression Trainer wip - adapter from QR decomposition to trainer
-- verified with diffs overview, clean build and execution of unit tests

commit 608d558fa33e61d86b35621ea706819621a017ba
Author: Oleg Ignatenko 
Date:   2017-11-27T16:16:19Z

IGNITE-6872 Linear regression should implement Model API
- OLS regression Trainer implemented
-- verified with diffs overview, clean build, execution of unit tests and 
examples

commit 857c0f83a281f9a37664988a50f2924f26140f47
Author: Oleg Ignatenko 
Date:   2017-12-07T11:04:41Z

Merge branch 'ignite-6872-2' into ignite-6872-4

# Conflicts:
#   modules/ml/src/test/java/org/apache/ignite/ml/LocalModelsTest.java
#   
modules/ml/src/test/java/org/apache/ignite/ml/regressions/DistributedBlockOLSMultipleLinearRegressionTest.java
#   

[GitHub] ignite pull request #3167: IGNITE-6872 Linear regression should implement Mo...

[oignatenko]

Github user oignatenko closed the pull request at:

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


---

[GitHub] ignite pull request #3167: IGNITE-6872 Linear regression should implement Mo...

[oignatenko]

GitHub user oignatenko opened a pull request:

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

IGNITE-6872 Linear regression should implement Model API



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

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

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

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


commit cf6ba40c97840a28ee14f49f09f79fe3d9d5a66f
Author: Oleg Ignatenko 
Date:   2017-11-20T11:53:46Z

IGNITE-6872 Linear regression should implement Model API
- regression examples moved to more appropriate package
-- verified with diffs overview, clean build and execution of unit tests

commit a8dadee71e0ca2a00387cfa2dba9c656de75137f
Author: Oleg Ignatenko 
Date:   2017-11-20T11:57:18Z

IGNITE-6872 Linear regression should implement Model API
- added missing package-info
-- verified with diffs overview

commit cc8edfbd0ca7e20655f45dc82d576f2d21627497
Author: Oleg Ignatenko 
Date:   2017-11-20T14:12:03Z

IGNITE-6872 Linear regression should implement Model API
- implementation, tests and examples
- accommodated changes done to OLS per IGNITE-5846
- fixed some issues with coding style and javadoc
-- verified with diffs overview, clean build, execution of unit tests and 
examples

commit a0f294740b78dbe354a67a1658c9877544e587ea
Author: Oleg Ignatenko 
Date:   2017-11-21T08:57:27Z

IGNITE-6872 Linear regression should implement Model API
- decision trees example moved to more appropriate package
-- verified with diffs overview

commit e944568849d09f2bc7fca932bc043304208ff55d
Author: Oleg Ignatenko 
Date:   2017-11-21T13:25:31Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit dfa4ea896d404b7bd231b57e880b5745b9db634f
Author: Oleg Ignatenko 
Date:   2017-11-21T13:37:47Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit fe79868659d9a04d73234d800b7e5b1ba9029eeb
Author: Oleg Ignatenko 
Date:   2017-11-21T13:38:19Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit c69583b91eef73616827cbfe03ad9eb1ff7ccde0
Author: Oleg Ignatenko 
Date:   2017-11-21T13:42:56Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit 1ca1fb030d5be32843fce9746aa7d026a81d4502
Author: Oleg Ignatenko 
Date:   2017-11-21T13:45:15Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview

commit 35918b024bca13dea3a061f623f743ab33f14cd7
Author: Oleg Ignatenko 
Date:   2017-11-21T13:49:53Z

IGNITE-6872 Linear regression should implement Model API
- corrections per review
-- verified with diffs overview, clean build, execution of unit tests and 
examples

commit 88fe344b83b9c9272eddc1c6e536febb0f8eff43
Author: Oleg Ignatenko 
Date:   2017-11-23T14:50:47Z

IGNITE-6872 Linear regression should implement Model API
- OLS regression Trainer wip - preliminary cleanup of QR decomposition
-- verified with diffs overview, clean build, execution of unit tests and 
examples

commit 24a27d9976fe5c1cf3ab876e410b4af63aec8792
Author: Oleg Ignatenko 
Date:   2017-11-23T15:26:20Z

IGNITE-6872 Linear regression should implement Model API
- OLS regression Trainer wip - adapter from QR decomposition to trainer
-- verified with diffs overview, clean build and execution of unit tests

commit 608d558fa33e61d86b35621ea706819621a017ba
Author: Oleg Ignatenko 
Date:   2017-11-27T16:16:19Z

IGNITE-6872 Linear regression should implement Model API
- OLS regression Trainer implemented
-- verified with diffs overview, clean build, execution of unit tests and 
examples

commit 6aca220e1a40609b5d2a283a338a9f9bdecdfe33
Author: Oleg Ignatenko 
Date:   2017-12-07T10:01:26Z

Merge branch 'ignite-6872-2' into ignite-6872-3

# Conflicts:
#   modules/ml/src/test/java/org/apache/ignite/ml/LocalModelsTest.java
#   
modules/ml/src/test/java/org/apache/ignite/ml/regressions/DistributedBlockOLSMultipleLinearRegressionTest.java
#   
modules/ml/src/test/java/org/apache/ignite/ml/regressions/DistributedOLSMultipleLinearRegressionTest.java




---

[GitHub] ignite pull request #3166: IGNITE-7134 Never-ending timeout in IgniteSpiOper...

[akuramshingg]

GitHub user akuramshingg opened a pull request:

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

IGNITE-7134 Never-ending timeout in 
IgniteSpiOperationTimeoutHelper.nextTimeoutChunk().



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

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

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

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


commit 982f91a695442a4f2a63f7dc96761f7cc87a25cf
Author: Alexandr Kuramshin 
Date:   2017-12-07T10:10:02Z

IGNITE-7134 Never-ending timeout in 
IgniteSpiOperationTimeoutHelper.nextTimeoutChunk().




---

Re: Ignite in docker (Native Persistence)

[Nikolai Tikhonov]

Hello!

Yes, sure! I'll investigate this question and update our doc.

On Thu, Dec 7, 2017 at 9:57 AM, Denis Magda  wrote:

> Nick,
>
> As one of Ignite docker maintainers, could you please investigate one how
> to map Ignite persistence to docker volumes:
> https://docs.docker.com/engine/admin/volumes/volumes/#
> use-a-read-only-volume
>
> and update the docker documentation:
> https://apacheignite.readme.io/docs/docker-deployment
>
> —
> Denis
>
> On Dec 1, 2017, at 8:40 AM, afedotov  wrote:
>
> Hi,
>
> You need to create volumes and map them to the ${IGNITE_HOME}/work/db or
> any
> other path that
> you might have specified via setPersistentStorePath. These volumes should
> outlive the Ignite containers
> and thus it will be possible to reuse them on restart.
>
> It's worth trying docker-compose, docker-swarm or kubernetes, depending on
> your needs.
> For example, Kubernetes provides a wide variety of volume options
> https://kubernetes.io/docs/concepts/storage/volumes/
>
>
> Has anyone use Ignite Native Persistence with Docker?
> Is there a solution on how to map the Volume dynamically? And how about
> when
> you restart the whole cluster, how does it maps all volumes?
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>
>

Re: Time and scope for Apache Ignite 2.4

[Igor Sapego]

Hi Denis,

I've been working on SSL support for ODBC [1] for a while now, and I hope
to include it in 2.4, as well as some other minor improvements and bug fixes
for ODBC.

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

Best Regards,
Igor

On Thu, Dec 7, 2017 at 11:51 AM, vveider  wrote:

> Hi, Denis.
>
> https://issues.apache.org/jira/browse/IGNITE-7107
> https://issues.apache.org/jira/browse/IGNITE-7108
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[jira] [Created] (IGNITE-7137) Provide a way to switch off BaselineTopology validation of nodes joining the cluster

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-7137:
---

 Summary: Provide a way to switch off BaselineTopology validation 
of nodes joining the cluster
 Key: IGNITE-7137
 URL: https://issues.apache.org/jira/browse/IGNITE-7137
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Reporter: Sergey Chugunov


In specific circumstances like split-brain user may need an ability to switch 
BaselineTopology validation off for a period of time when the cluster is 
assembling back.

To do so we need to provide an API to switch BaselineTopology validation on and 
off dynamically.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Time and scope for Apache Ignite 2.4

[vveider]

Hi, Denis.

https://issues.apache.org/jira/browse/IGNITE-7107
https://issues.apache.org/jira/browse/IGNITE-7108



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

[jira] [Created] (IGNITE-7136) Add JMX metric for indexing to .Net

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-7136:
---

 Summary: Add JMX metric for indexing to .Net 
 Key: IGNITE-7136
 URL: https://issues.apache.org/jira/browse/IGNITE-7136
 Project: Ignite
  Issue Type: Sub-task
  Components: platforms
Reporter: Nikolay Izhikov
Assignee: Pavel Tupitsyn


New JMX metric implemented in IGNITE-6903.
We need to add support for this metric to .Net 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-7135) IgniteCluster.startNodes() returns successful ClusterStartNodeResult even though the remote process fails

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-7135:
--

 Summary: IgniteCluster.startNodes() returns successful 
ClusterStartNodeResult even though the remote process fails
 Key: IGNITE-7135
 URL: https://issues.apache.org/jira/browse/IGNITE-7135
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Alexandr Kuramshin
 Fix For: 2.4


After unsuccessful start of three remote nodes with 
{{IgniteCluster#startNodes(Collection>, Map, 
boolean, int, int)}} we get {{Collection}} with three 
elements, each has {{isSuccess()}} is true.

But the remote node startup log was
{noformat}
nohup: ignoring input
/data/teamcity/work/820be461cd64b574/bin/ignite.sh, ERROR:
The version of JAVA installed in JAVA_HOME=/usr/lib/jvm/java-9-oracle is 
incorrect.
Please point JAVA_HOME variable to installation of JDK 1.7 or JDK 1.8.
You can also download latest JDK at http://java.com/download
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #3165: IGNITE-6711: TotalAllocatedPages metric fix.

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-6711: TotalAllocatedPages metric fix.



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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6711

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

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


commit e6c75e81b87ec7e4e2489dd6a96e2f5a0b3d0c89
Author: Andrey Kuznetsov 
Date:   2017-12-07T08:23:47Z

IGNITE-6711: TotalAllocatedPages metric fix.




---

[jira] [Created] (IGNITE-7134) Never-ending timeout in IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()

[Alexandr Kuramshin (JIRA)]

Alexandr Kuramshin created IGNITE-7134:
--

 Summary: Never-ending timeout in 
IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()
 Key: IGNITE-7134
 URL: https://issues.apache.org/jira/browse/IGNITE-7134
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.3
Reporter: Alexandr Kuramshin
Priority: Critical
 Fix For: 2.4


{noformat}
org.apache.ignite.spi.IgniteSpiOperationTimeoutHelper#nextTimeoutChunk

long curTs = U.currentTimeMillis();

timeout = timeout - (curTs - lastOperStartTs);
{noformat}

Timeout will not be decreased at all if delay between successive calls to 
nextTimeoutChunk() is smaller than U.currentTimeMillis() discretization. Such 
behaviour could be easily achieved when getting an error right after the 
nextTimeoutChunk() invocation and do the retry.

Only rare calls (the first right before U.currentTimeMillis() and the second 
right after that) may decrease timeout, so actual 
IgniteSpiOperationTimeoutHelper timeout could be much bigger than the 
failureDetectionTimeout.

My opinion to not split failureDetectionTimeout between network operations, but 
initialize first operation timestamp at first call to nextTimeoutChunk(), and 
then calculate the timeout as a difference between the current timestamp and 
the first operation timestamp.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)