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
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
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
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4102
---
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 user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4190
---
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
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 t
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/4178
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4090
---
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 requ
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4061
---
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-8
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/
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
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
Github user NSAmelchev closed the pull request at:
https://github.com/apache/ignite/pull/4021
---
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://githu
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 appl
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
Proj
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 igni
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
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4170
---
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/4203
IGNITE-8180
Fixed test ZookeeperDiscoverySpiTest#testQuorumRestore.
Sometimes nodes don't have time to reconnect and loses connections. I
increased session timeout.
You can merge this pull
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 i
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 grp
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:
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 wai
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
Alternative
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4205
---
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: Ignit
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
Altern
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?
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 wh
+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
35 matches
Mail list logo
