Re: Separate binaries for thin clients and drivers

[Dmitriy Setrakyan]

+1

On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda  wrote:

> Igniters,
>
> Presently, all our thin clients and SQL drivers are stored in the main
> Ignite repository. That's totally fine, I wouldn't change anything in here.
>
> But, what I would encourage us to contemplate on is how a user gets and
> downloads those binaries. Basically, the user has to download the whole
> Ignite distribution even if he needs just a JDBC driver or Node.JS thin
> driver.
>
> The proposal is pretty simple. In addition to the main distribution, let's
> prepare separate ZIP archives with binaries for:
>
>- JDBC
>- ODBC
>- Thin clients (Java, C#, Node.JS, Python, etc.)
>
> The binaries would be available for downloads on the main page:
> https://ignite.apache.org/download.cgi
>
> Thoughts? Supporters and opposers, please speak out.
>
> --
> Denis
>

Separate binaries for thin clients and drivers

[Denis Magda]

Igniters,

Presently, all our thin clients and SQL drivers are stored in the main
Ignite repository. That's totally fine, I wouldn't change anything in here.

But, what I would encourage us to contemplate on is how a user gets and
downloads those binaries. Basically, the user has to download the whole
Ignite distribution even if he needs just a JDBC driver or Node.JS thin
driver.

The proposal is pretty simple. In addition to the main distribution, let's
prepare separate ZIP archives with binaries for:

   - JDBC
   - ODBC
   - Thin clients (Java, C#, Node.JS, Python, etc.)

The binaries would be available for downloads on the main page:
https://ignite.apache.org/download.cgi

Thoughts? Supporters and opposers, please speak out.

--
Denis

Re: Service grid redesign

[Denis Magda]

Hi Vyacheslav,

If to assume that Ignite 2.7 gets released in September, what else would
you be able to complete by that time? I would see how to promote this from
the community side (articles, webinars, meetups).

Plus, do you think you'll be able to complete the whole IEP by the end of
the year? Is someone else going to help you with this initiative? That
would be a huge New Year gift to Ignite community.

--
Denis

On Thu, Jun 7, 2018 at 11:51 AM Vyacheslav Daradur 
wrote:

> Hi Igniters, sorry for the delay in replying.
>
> I going to finish the task [1] to the end of this month.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8361
>
> On Wed, May 16, 2018 at 10:57 PM, Vyacheslav Daradur
>  wrote:
> > Hi, Igniters!
> >
> > I had a discussion about the scope of work of IEP-17 with Denis and
> Pavel.
> >
> > To estimate the time I took 2 weeks for R during which I would do the
> task:
> > https://issues.apache.org/jira/browse/IGNITE-8361
> >
> > Then I will inform the community about the planned work time.
> >
> >
> > On Tue, May 8, 2018 at 9:50 PM, Vyacheslav Daradur 
> wrote:
> >> Thanks, Denis! I assigned the task to myself.
> >>
> >> I going to start work next week.
> >>
> >> On Tue, May 8, 2018 at 7:50 PM, Denis Mekhanikov 
> wrote:
> >>> Hi Vyacheslav!
> >>>
> >>> Thanks for the enthusiasm!
> >>> The first ticket to be implemented here is IGNITE-8361
> >>> .
> >>> I think, until this one is resolved, other tasks can't be started.
> >>>
> >>> Please assign it to yourself, if you feel confident enough.
> >>> Feel free to ask for any help, if you need.
> >>>
> >>> For now it will be enough to perform service deployment and
> initialization
> >>> in the discovery thread.
> >>> Making it asynchronous will be our next step: IGNITE-8362
> >>> 
> >>>
> >>> Denis
> >>>
> >>> вт, 24 апр. 2018 г. в 15:43, Vyacheslav Daradur :
> >>>
>  Hi, Denis M.,
> 
>  I'd like to pick up a ticket from IEP-17 next week.
> 
>  Could you please advise a ticket to start?
> 
>  On Tue, Apr 24, 2018 at 11:47 AM, Dmitriy Setrakyan
>   wrote:
>  > On Tue, Apr 24, 2018, 3:59 PM Denis Mekhanikov <
> dmekhani...@gmail.com>
>  > wrote:
>  >
>  >> Dmitriy,
>  >>
>  >> After the proposed changes are made the utility cache won't be
> needed at
>  >> all.
>  >>
>  >
>  > I was rather talking about prioritization. In my view, first and
> foremost
>  > we must fix deployment before anything else.
>  >
>  > D.
> 
> 
> 
>  --
>  Best Regards, Vyacheslav D.
> 
> >>
> >>
> >>
> >> --
> >> Best Regards, Vyacheslav D.
> >
> >
> >
> > --
> > Best Regards, Vyacheslav D.
>
>
>
> --
> Best Regards, Vyacheslav D.
>

[GitHub] ignite pull request #4206: IGNITE-8769: research (IgniteBasicTestSuite contr...

[x-kreator]

GitHub user x-kreator opened a pull request:

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

IGNITE-8769: research (IgniteBasicTestSuite contraction)



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

$ git pull https://github.com/x-kreator/ignite ignite-8769

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

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


commit 369e7e366d3e426c60e19efc2134351494b78107
Author: Dmitriy Sorokin 
Date:   2018-06-15T18:17:52Z

IGNITE-8769: research (IgniteBasicTestSuite contraction)




---

[jira] [Created] (IGNITE-8811) Create copies of basic TC suites with PDS delta checking framework enabled

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-8811:
--

 Summary: Create copies of basic TC suites with PDS delta checking 
framework enabled
 Key: IGNITE-8811
 URL: https://issues.apache.org/jira/browse/IGNITE-8811
 Project: Ignite
  Issue Type: Bug
 Environment: With having PDS delta checking framework implemented 
(IGNITE-8529), we should add some copies of existing TC suites with system 
property that enables self-check on checkpoint.
We can start with Full API and SQL suites. Please note that some tests may fail 
with OOM as Ignite node with framework consumes x2 RAM.
Reporter: Ivan Rakov
Assignee: Ivan Rakov






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4205: IGNITE-8792: TF integration module

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4205: IGNITE-8792: TF integration module

[ybabak]

GitHub user ybabak opened a pull request:

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

IGNITE-8792: TF integration module

initial commit

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

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

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

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


commit 5bb52f1cbbcae9301b6d9cf092c03ca9ec350b89
Author: YuriBabak 
Date:   2018-06-15T12:07:21Z

IGNITE-8792: TF integration module

initial commit

commit 2629b5f90733283bd8be58e481556f113cac6b5b
Author: YuriBabak 
Date:   2018-06-15T16:39:58Z

IGNITE-8792: TF integration module

Readme fix

commit c4296aedc7570ca195378ece8bce293e3df019ef
Author: Yury Babak 
Date:   2018-06-15T16:40:26Z

Merge branch 'apacheMaster' into ignite-8792




---

Re: Need review IGNITE-8661

[Ivan Rakov]

Dmitriy G.,

I will take a look as well, just in case.

Best Regards,
Ivan Rakov

On 15.06.2018 2:36, Dmitriy Setrakyan wrote:

Dmitriy, great job! Very important fix to a very bad problem in the product
that could cause data consistency issue.

Will it be included into 2.6, or will we have to wait for 2.7?

D.

On Thu, Jun 14, 2018 at 6:53 AM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:


Folks,

I fixed a problem with an iterator. [1] WALItreater is not stopped if can
not deserialize record or fail read record with corrupted content. Please
review [2][3].

[1] IGNITIGNITE-8661 
[2] PR-4155 
[3] CR-637 

dev-list discussion: WAL iterator unexpected behavior

[jira] [Created] (IGNITE-8810) Create failoverSafe for ReentrantLock

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-8810:
-

 Summary: Create failoverSafe for ReentrantLock
 Key: IGNITE-8810
 URL: https://issues.apache.org/jira/browse/IGNITE-8810
 Project: Ignite
  Issue Type: Improvement
Reporter: Evgenii Zhuravlev


Currently, it has the flag "failoverSafe", but it doesn't have any 
implementation for it



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: unused or only used in tests methonds

[Alexey Goncharuk]

I have no objections to remove these methods.

--AG

чт, 14 июн. 2018 г. в 17:39, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com>:

> Igniters,
>
> I found 2 methods,
>
> 1. PageStore.pageOffset(long pageId) -  it unused, seem that old artifact.
> 2. IgnitePageStoreManager.pagesAllocated(int grpId) - used only in test,
> seem that same problem can be solved with
> IgnitePageStoreManager.pages(grpId,
> partId).
>
> I suggest, remove these methods for the more clear interface.
>
> Any reason, why we can not remove them?
>

[GitHub] ignite pull request #4204: IGNITE-8789 Invoke failure processor in case of m...

[agura]

GitHub user agura opened a pull request:

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

IGNITE-8789 Invoke failure processor in case of message processing error



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

$ git pull https://github.com/agura/incubator-ignite ignite-8789

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

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


commit 7fed8d723500e243221734babe6981758363f874
Author: Andrey Gura 
Date:   2018-06-15T14:12:09Z

IGNITE-8789 Invoke failure processor in case of message processing error




---

[jira] [Created] (IGNITE-8809) Add ability to control.sh to force rebalance for specific partitions on given nodes.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-8809:
-

 Summary: Add ability to control.sh to force rebalance for specific 
partitions on given nodes.
 Key: IGNITE-8809
 URL: https://issues.apache.org/jira/browse/IGNITE-8809
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexei Scherbakov


Sometimes it's desirable to force rebalance for specific partitions on given 
nodes, for example, for test reasons or fixing synchronizations issues without 
nodes downtime.

control.sh should contain new command: rebalance, which will execute the 
exchange request carried by new message type, containing partitions for 
rebalancing and mode: full (evict + move) or delta (historical, using counters).

Example:

control.sh --rebalance [full|delta] nodeId:p1,p2,p3 node2:p4,p5 ...




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4202: IGNITE-8707 header is accounted during calculatio...

[akalash]

GitHub user akalash opened a pull request:

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

IGNITE-8707 header is accounted  during calculation allocated pages



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

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

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

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


commit 12da4de06d6405e437f04bdcfdfbb277425a9fb8
Author: Anton Kalashnikov 
Date:   2018-06-15T13:45:23Z

IGNITE-8707 header is accounted  during calculation allocated pages




---

[jira] [Created] (IGNITE-8808) Improve control.sh --tx command to show local and remote transactions.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-8808:
-

 Summary: Improve control.sh --tx command to show local and remote 
transactions.
 Key: IGNITE-8808
 URL: https://issues.apache.org/jira/browse/IGNITE-8808
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.5
Reporter: Alexei Scherbakov
Assignee: Alexei Scherbakov
 Fix For: 2.6


Currently --tx option for control.sh shows only transactions found on 
near(initiating) nodes.

Due to various issues it's possible to have corresponding dht local and remote 
transaction without near part.

Such transactions must be visible to utility.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4201: Ignite-2.5.1-p7

[EdShangGG]

GitHub user EdShangGG opened a pull request:

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

Ignite-2.5.1-p7



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

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

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

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


commit 1cea80d29f4f1c61ed56ad1261b74ed42611bf64
Author: Ilya Lantukh 
Date:   2018-04-06T10:49:10Z

IGNITE-8018 Optimized GridCacheMapEntry initialValue() - Fixes #3686.

Signed-off-by: Alexey Goncharuk 

commit 37fc72542eb6baa8be8b41aecd08a194102d13c1
Author: Алексей Стельмак 
Date:   2018-04-06T15:28:22Z

IGNITE-8049 Limit the number of operation cycles in B+Tree - Fixes #3769.

Signed-off-by: dpavlov 

(cherry picked from commit e491f10)

commit 76e293654e34c927d6c9efc85a12e736b58a21f2
Author: Eduard Shangareev 
Date:   2018-04-06T16:22:07Z

IGNITE-8114 Add fail recovery mechanism to tracking pages - Fixes #3734.

Signed-off-by: dpavlov 

(cherry picked from commit 0829397)

commit 49f11db727febc83297c7f0f5de9e6f98f0197fa
Author: Alexey Kuznetsov 
Date:   2018-04-09T02:25:50Z

IGNITE-8159 control.sh: Fixed NPE on adding nodes on empty baseline and not 
active cluster.

(cherry picked from commit 834869c)

commit 9ad7be2f51b6dcdcdf43fedb298cd4e240f0adab
Author: Ilya Borisov 
Date:   2018-04-09T13:59:32Z

IGNITE-8155 Web Console: Fixed number pattern warning in browser console.

(cherry picked from commit 5d8f570)

commit 4aa56751906e5db7aad025a7193933fa929aae26
Author: Vasiliy Sisko 
Date:   2018-04-09T15:13:21Z

IGNITE-7940 Visor CMD: Added "cache -slp" and "cache -rlp" commands to show 
and reset lost partitions for specified cache.

(cherry picked from commit abfa0f5)

commit cc04c5c70af1bdbba834f73330e73277b60e23fc
Author: Eduard Shangareev 
Date:   2018-04-09T16:15:50Z

IGNITE-8114 Additional fix for Add fail recovery mechanism to tracking pages

(cherry picked from commit 961fc35)

commit c70d85aa36c702ea0f29bd8668e9bf0790f9ba11
Author: Vasiliy Sisko 
Date:   2018-04-10T08:42:24Z

IGNITE-8126 Web Console: Fixed code generation for cache load.

(cherry picked from commit a0a187b)

commit 8d3755b9c58eef12c5fc9cabfc0b1c05f6db716e
Author: Semyon Boikov 
Date:   2018-04-10T08:37:39Z

IGNITE-7222 Added ZooKeeper discovery SPI

commit b096a463c338565a7661f8a853a257518d872997
Author: Stanislav Lukyanov 
Date:   2018-04-09T11:33:13Z

IGNITE-7904: Changed IgniteUtils::cast not to trim exception chains. This 
closes #3683.

commit 82a4c024fe06ef8c8deeaf762f0cc20a8e481252
Author: Roman Guseinov 
Date:   2018-04-09T11:45:44Z

IGNITE-7944: Disconnected client node tries to send JOB_CANCEL message. 
Applied fix:
- Skip sending message if client disconnected;
- Throw IgniteCheckedException if a client node is disconnected and 
communication client is null.
This closes #3737.

commit c1745de37891026e0a719f0c1d1afe768dfccbf3
Author: Vasiliy Sisko 
Date:   2018-04-10T10:48:52Z

IGNITE-7927 Web Console: Fixed demo for non-collocated joins.

(cherry picked from commit 647620b)

commit b28287d1861fd841a18d0eef95eff309d21a55ef
Author: Alexey Goncharuk 
Date:   2018-04-10T13:22:28Z

IGNITE-8025 Future must fail if assertion error has been thrown in the 
worker thread

commit a832f2b2e5788c45114c3cb5529d7cf53d08f9a6
Author: Andrey Kuznetsov 
Date:   2018-04-10T14:30:12Z

ignite-7772 System workers critical failures handling

Signed-off-by: Andrey Gura 

commit 912433ba9aa113508d05930691b251eccd8f5870
Author: Aleksey Plekhanov 
Date:   2018-04-10T15:54:03Z

IGNITE-8069 IgniteOutOfMemoryException should be handled accordingly to 
provided failure handler

Signed-off-by: Andrey Gura 

commit 99feab6ace66d011b677fd4d57b44fc54da8fd4f
Author: Alexey Goncharuk 
Date:   2018-04-10T17:33:47Z

IGNITE-6430 Complete failing test early

commit 526fb0ee612ef71fde58a1274db35e8205304a63
Author: Dmitriy Sorokin 
Date:   2018-04-10T19:20:41Z

IGNITE-8101 Ability to terminate system workers by JMX for test purposes.

Signed-off-by: Andrey Gura 

commit b4cb2f0df944534743a9d73811e047eda572258c
Author: mcherkasov 
Date:   2018-04-11T00:27:20Z

IGNITE-8153 Nodes fail to connect each other when SSL is enabled - Fixes 
#3773.

Signed-off-by: Valentin Kulichenko 

commit b4cc9f2d45d78c360abe224165e707c23533469e
Author: Pavel Kovalenko 
Date:   2018-04-11T08:23:46Z

IGNITE-7871 Implemented additional synchronization phase for correct 
partition counters update

commit 9abfee69aa153888456f9e8574ece1f2d0cbe4d9
Author: dmitrievanthony 
Date:   2018-04-10T09:46:43Z

IGNITE-8059: Integrate 

[GitHub] ignite pull request #4200: IGNITE-8749: Exception for "no space left" situat...

[x-kreator]

GitHub user x-kreator opened a pull request:

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

IGNITE-8749: Exception for "no space left" situation should be propag…

…ated to FailureHandler.

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

$ git pull https://github.com/x-kreator/ignite ignite-8749

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

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


commit de762f1afa3b0d41442758985cf60a1601dff6fc
Author: Dmitriy Sorokin 
Date:   2018-06-15T09:48:42Z

IGNITE-8749: Exception for "no space left" situation should be propagated 
to FailureHandler.




---

[GitHub] ignite pull request #4021: IGNITE-6010

[NSAmelchev]

Github user NSAmelchev closed the pull request at:

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


---

[GitHub] ignite pull request #4199: IGNITE-8798 log level for transaction recovery st...

[ezagumennov]

GitHub user ezagumennov opened a pull request:

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

IGNITE-8798 log level for transaction recovery state changes changed …

…to INFO

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

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

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

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


commit 3edcc17649c98f002133d5256f7d987488342b35
Author: ezagumennov 
Date:   2018-06-15T11:50:59Z

IGNITE-8798 log level for transaction recovery state changes changed to INFO




---

Re: Upgrading Ignite to JCache 1.1

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

Denis, I think we can include it to a minor release. Because the network
protocol, API, binary compatibility will be saved. And all behavior
changes, in fact, make implementation closer to the documentation of JCache
1.0. Because TCK 1.1.0 in general fixes differents between documentation
and tests in 1.0.

2018-06-14 21:41 GMT+03:00 Denis Magda :

> Guys, are you targeting this for the next big Ignite release? Should be in
> 3 m from now.
>
> --
> Denis
>
> On Thu, Jun 14, 2018 at 2:58 AM Anton Vinogradov  wrote:
>
> > Corrected IEP URL:
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 21%3A+JCache+1.1+support
> >
> > чт, 14 июн. 2018 г. в 12:48, Александр Меньшиков :
> >
> > > Igniters,
> > >
> > > I've prepared IEP-21 [1] for this JCache updating task.
> > > It will help us to manage the issues and see the progress in one place.
> > > Also, we have finally added tests for TCK 1.1.0 [2] to our TC which can
> > be
> > > run on any branch.
> > > Both tests cases (for 1.0.1 and for 1.1.0) will coexist until IEP-21
> > > finish.
> > >
> > > [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-21:+JCache+1.1
> > > [2]
> > >
> > >
> > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> IgniteTests24Java8_JCacheTck11
> > >
> > > 2018-06-06 0:49 GMT+03:00 Denis Magda :
> > >
> > > > Agree, I see zero benefits of being compliant with both specification
> > > > versions. Let’s just focus on the latest one.
> > > >
> > > > Denis
> > > >
> > > > On Tuesday, June 5, 2018, Dmitriy Setrakyan 
> > > wrote:
> > > >
> > > > > Alex,
> > > > >
> > > > > I think it is OK to break TCK 1.0.1 tests in favor of TCK 1.1. Once
> > we
> > > > > finish the migration, I would remove the TCK 1.0.1 test suite
> > > altogether.
> > > > >
> > > > > D.
> > > > >
> > > > > On Tue, Jun 5, 2018 at 11:13 AM, Александр Меньшиков <
> > > > sharple...@gmail.com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > Okay. There are tests results:
> > > > > >
> > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1361493;
> > > > > > tab=buildResultsDiv=IgniteTests24Java8_JCacheTck11
> > > > > >
> > > > > > It's the same as locally.
> > > > > >
> > > > > > Also, I have created sub-tasks for all problems we have:
> > > > > >
> > > > > > 1) CacheManagerTest.getUnsafeTypedCacheRequest failed.
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8704
> > > > > >
> > > > > > 2) CacheMBStatisticsBeanTest.testClear failed.
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8705
> > > > > >
> > > > > > 3) CacheManagerTest.close_cachesEmpty failed.
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8708
> > > > > >
> > > > > > 4) CacheMBStatisticsBeanTest.testPutIfAbsent failed.
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8709
> > > > > >
> > > > > > 5) CacheEntryEvent.getOldValue should be available.
> > > > > > Two tests fail because of it.
> > > > > >
> > > > > > Looks like a bug.
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8714
> > > > > >
> > > > > > 6) Problems with Closeable objects from Factory
> > > > > >
> > > > > > *98* tests fail because of it.
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8715
> > > > > >
> > > > > >
> > > > > > For first 4 problems, I already have PRs.
> > > > > > Problems 2) and 3) will break tests for TCK 1.0.1 because these
> > tests
> > > > > work
> > > > > > wrong in 1.0.1,
> > > > > > and were fixed in 1.1.0.
> > > > > >
> > > > > > 2018-06-05 14:37 GMT+03:00 Dmitry Pavlov  >:
> > > > > >
> > > > > > > Agree with Nikolay we should create build plan, and we can use
> > this
> > > > > build
> > > > > > > plan in developement branch.
> > > > > > >
> > > > > > > Merge to master is not necessary before issue is ready.
> > > > > > >
> > > > > > > вт, 5 июн. 2018 г. в 14:04, Nikolay Izhikov <
> nizhi...@apache.org
> > >:
> > > > > > >
> > > > > > >> Alex, please try to run this build plan for your branch
> > > > > > >>
> > > > > > >> https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > > > >> IgniteTests24Java8_JCacheTck11
> > > > > > >>
> > > > > > >> В Вт, 05/06/2018 в 13:56 +0300, Nikolay Izhikov пишет:
> > > > > > >> > Guys, we had a private talk with Vyacheslav and Dmitriy
> > Pavlov.
> > > > > > >> > Here are its resulst:
> > > > > > >> >
> > > > > > >> > 1. I will create JCache1.1 build plan.
> > > > > > >> > I will be able to run tests with Alex new profile enabled.
> > > > > > >> >
> > > > > > >> > So, Alex can run and share with community tests results both
> > for
> > > > > > jcache
> > > > > > >> 1.0 and jcache 1.1.
> > > > > > >> >
> > > > > > >> > 2. Alex, please, create tickets for a JCache 1.1. issues.
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > В Вт, 05/06/2018 в 13:36 +0300, Vyacheslav Daradur пишет:
> > > > > > >> > > AFAIK TeamCity is not able to create such build-plan on
> the
> > > fly.
> > > > > > >> > > Moreover, we will not be able to test master branch in
> both
> > > > > 

[GitHub] ignite pull request #4197: IGNITE-8594

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

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

IGNITE-8594

Make error messages in validate_indexes command report more informative

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

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

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

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


commit 969fc9851cc0f3a6c55dacf9a8d7ca05c52fb02c
Author: vd-pyatkov 
Date:   2018-06-15T10:49:44Z

IGNITE-8594
Make error messages in validate_indexes command report more informative




---

[GitHub] ignite pull request #4198: IGNITE-8738 log "coordinator changed" message in ...

[ezagumennov]

GitHub user ezagumennov opened a pull request:

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

IGNITE-8738 log "coordinator changed" message in every node



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

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

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

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


commit 1e537d4a11ea86a5003b50a2287dd1d1924c5f20
Author: ezagumennov 
Date:   2018-06-15T10:48:55Z

IGNITE-8738 log "coordinator changed" message in every node




---

[GitHub] ignite pull request #4061: IGNITE-8605 Specify jline minor version to fix nc...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4196: IGNITE-8755: If size is too big and left shift ca...

[ivandasch]

GitHub user ivandasch opened a pull request:

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

IGNITE-8755: If size is too big and left shift can cause arithmetic o…

…veflow, just allocate bytes for required size. So NegativeArrayException 
will never throw

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

$ git pull https://github.com/ivandasch/ignite ignite-8755

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

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


commit 0a77d3d2cd9713669e756078f0231faee743c7c1
Author: Ivan Daschinskiy 
Date:   2018-06-15T10:16:40Z

IGNITE-8755: If size is too big and left shift can cause arithmetic 
oveflow, just allocate bytes for required size.




---

[GitHub] ignite pull request #4090: IGNITE-8610 Checkpoint history search fix + refac...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4178: IGNITE-8763 java.nio.file.AccessDeniedException i...

[alex-plekhanov]

Github user alex-plekhanov closed the pull request at:

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


---

[GitHub] ignite pull request #4195: IGNITE-8807 Apache Ignite Linux packages 2.6 upda...

[vveider]

GitHub user vveider opened a pull request:

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

IGNITE-8807 Apache Ignite Linux packages 2.6 update

 * update packages' version to 2.6.0
 * added dirmngr dependency for DEB package for Debian apt-key
network compatibility

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

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

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

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


commit 5124c4fc8c3a3f5c5a3ac1db15a061f78826a187
Author: Ivanov Petr 
Date:   2018-06-15T09:03:25Z

IGNITE-8807 Apache Ignite Linux packages 2.6 update
 * update packages' version to 2.6.0
 * added dirmngr dependency for DEB package for Debian apt-key
network compatibility




---

[jira] [Created] (IGNITE-8807) Apache Ignite Linux packages 2.6 update

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-8807:


 Summary: Apache Ignite Linux packages 2.6 update
 Key: IGNITE-8807
 URL: https://issues.apache.org/jira/browse/IGNITE-8807
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov
 Fix For: 2.6


Update RPM and DEB packages' specifications for 2.6 release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4190: IGNITE-8800

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Ignite 2.6 emergency release suggestion

[Petr Ivanov]

Igniters,


I’d like to stage for 2.6 release also this issue [1]. Corresponding PR [2] is 
ready for review and merge.
This is not related to code additional configuration file for enabling support 
of Windows 10 WSL Environment.


[1] https://issues.apache.org/jira/browse/IGNITE-8804
[2] https://github.com/apache/ignite/pull/4194



> On 14 Jun 2018, at 06:59, Alexey Kuznetsov  wrote:
> 
> Hi,
> 
> Fix for IGNITE-8722 (https://issues.apache.org/jira/browse/IGNITE-8722) is
> ready.
> 
> Diff
> 
> https://git1-us-west.apache.org/repos/asf?p=ignite.git=search=refs%2Fheads%2Fignite-8722=commit=IGNITE-8722
> 
> TC looks good for me.
> 
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195=buildResultsDiv=IgniteTests24Java8_JavaClient
> 
> I'm ready to merge to master and 2.6 branches.
> Please approve.
> 
> -- 
> Alexey Kuznetsov

[GitHub] ignite pull request #4102: IGNITE-8657 client reconnect on exchange history ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4194: IGNITE-8804 Windows WSL configuration has to be a...

[vveider]

GitHub user vveider opened a pull request:

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

IGNITE-8804 Windows WSL configuration has to be added to Ignite configs



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

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

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

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


commit d9f2e792cefdc51e8bfd546db46760f5ddac3620
Author: Ivanov Petr 
Date:   2018-06-15T08:31:08Z

IGNITE-8804 Windows WSL configuration has to be added to Ignite configs




---

[GitHub] ignite pull request #4193: IGNITE-8806

[devozerov]

GitHub user devozerov opened a pull request:

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

IGNITE-8806



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

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

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

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


commit 8b5d718edcf357234fa639ae57175141be321173
Author: devozerov 
Date:   2018-06-15T08:16:52Z

IGNITE-8806: Fixed.




---

[jira] [Created] (IGNITE-8806) SQL: NPE in GridH2ProxyIndex when trying to access lookup batch

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-8806:
---

 Summary: SQL: NPE in GridH2ProxyIndex when trying to access lookup 
batch
 Key: IGNITE-8806
 URL: https://issues.apache.org/jira/browse/IGNITE-8806
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.5
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.6


See {{GridH2ProxyIndex#createLookupBatch}} - it calls the same method on real 
index and returns wrapped batch unconditionally.

But according to the contract of this method, index may return {{null}}. Proxy 
index should return {{null}} in this case as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)