Re: Future of Ignite transactions

Vladimir, This looks like a complete overhaul of our transactional behavior and I do not think we are at a liberty to make such drastic changes. Can you please explain why the current behavior would not map to the SQL transactions? D. On Mon, Sep 25, 2017 at 12:09 PM, Vladimir Ozerov

Re: Persistence per memory policy configuration

Given that we already have a notion of CacheStore which comes from JCache spec, I think having other stores may get confusing. I like DurableMemoryConfiguration. Other opinions? D. On Mon, Sep 25, 2017 at 12:24 PM, Vladimir Ozerov wrote: > Dima, let's finalize the design

[jira] [Created] (IGNITE-6498) Web console: Query metadata should show table alias when configured

Vasiliy Sisko created IGNITE-6498: - Summary: Web console: Query metadata should show table alias when configured Key: IGNITE-6498 URL: https://issues.apache.org/jira/browse/IGNITE-6498 Project:

Re: Issues if -Djava.net.preferIPv4Stack=true is not set

Yakov, Here are couple examples: - http://apache-ignite-users.70518.x6.nabble.com/How-to- correctly-shut-down-Ignite-Application-td12548.html - http://apache-ignite-users.70518.x6.nabble.com/Nodes- hanging-when-accessing-queue-td12343.html *Andrey*, it seems that you give this kind of

Re: Warning if no table for BinaryObject

Pavel, we can optionally enforce that, but not by default. Dmitry, the problem is the following. User configures Ignite cache and query entity, does several puts than empty results for SQL. The reason is very simple - typo in class name or simply different classes in configuration and of actual

Re: Apache Ignite 2.3 release

Hi Vladimir! Could you add to future release by PR (http://apache-ignite-developers.2346864.n4.nabble.com/GitHub-ignite-pull-request-2737-IGNITE-6286-fix-org-h2-jdbc-JdbcSQLException-td22625.html)? The PR is very important for project Hibernate OGM . -- Sent from:

Re: Warning if no table for BinaryObject

On Fri, Sep 22, 2017 at 9:47 AM, Mikhail Cherkasov wrote: > Hi all, > > I've seen several times that due wrong cache configuration people can't > find > data in cache and blame Ignite that it's buggy and doesn't work. > > And it's very difficult to find an error in the

[GitHub] ignite pull request #2641: ignite-5960 continuous query entry update race fi...

Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2641 ---

[GitHub] ignite pull request #2668: ignite-5960 race fixed

Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2668 ---

[GitHub] ignite pull request #2741: IGNITE-6494 .NET: Fix CacheConfiguration.WriteSyn...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2741 IGNITE-6494 .NET: Fix CacheConfiguration.WriteSynchronizationMode default value You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-6494) .NET: CacheConfiguration.WriteSynchronizationMode incorrect default value

Pavel Tupitsyn created IGNITE-6494: -- Summary: .NET: CacheConfiguration.WriteSynchronizationMode incorrect default value Key: IGNITE-6494 URL: https://issues.apache.org/jira/browse/IGNITE-6494

[GitHub] ignite pull request #2740: IGNITE-6242

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2740 IGNITE-6242 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6242 Alternatively you can review and apply

[GitHub] ignite pull request #2737: IGNITE-6286: fix org.h2.jdbc.JdbcSQLException

GitHub user schernolyas opened a pull request: https://github.com/apache/ignite/pull/2737 IGNITE-6286: fix org.h2.jdbc.JdbcSQLException changes: 1) develop test for check all supported types for parameterized queries 2) add support BigDecimal type as type of paraameter's

Re: Apache Ignite 2.3 release

You can find the list of 2.3 tickets which are either reported by you or assigned to you using this report [1]. Please make sure that this list is relevant and tickets will be completed in a matter of 2 weeks. NB: You should be logged in to JIRA. [1]

Re: Warning if no table for BinaryObject

We could even add a configuration switch to throw an exception in such case. I guess that in majority of use cases there is a single type per cache, and we should have a way to enforce that. On Fri, Sep 22, 2017 at 7:47 PM, Mikhail Cherkasov wrote: > Hi all, > > I've

Re: Apache Ignite 2.3 release

Hi Vladimir! Could you please add my PR to next relese. I mean PR https://github.com/apache/ignite/pull/2737 . The PR is very important for project Hibernate OGM. A lot of thanks! With best regards, Sergey Chernolyas -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Apache Ignite 2.3 release

Hi, For Ignite.NET I would like to include at least these two: https://issues.apache.org/jira/browse/IGNITE-5615 .NET: IgniteConfiguration.LocalEventListeners https://issues.apache.org/jira/browse/IGNITE-4070 .NET: Introduce transformers to SCAN queries Also users are asking for .NET Core and

[GitHub] ignite pull request #2739: IGNITE-6360: NPE occurs if object with null index...

GitHub user mcherkasov opened a pull request: https://github.com/apache/ignite/pull/2739 IGNITE-6360: NPE occurs if object with null indexed field is added You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2628: IGNITE-6301: Unused variable removed.

Github user nizhikov closed the pull request at: https://github.com/apache/ignite/pull/2628 ---

[GitHub] ignite pull request #2663: Ignite 3084 - pre alpha to share with AV

Github user nizhikov closed the pull request at: https://github.com/apache/ignite/pull/2663 ---

[jira] [Created] (IGNITE-6495) performance measurement of decision trees algorithms

Oleg Ignatenko created IGNITE-6495: -- Summary: performance measurement of decision trees algorithms Key: IGNITE-6495 URL: https://issues.apache.org/jira/browse/IGNITE-6495 Project: Ignite

[GitHub] ignite pull request #2742: IGNITE-3084: Prototype of Ignite DataFrame suppor...

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/2742 IGNITE-3084: Prototype of Ignite DataFrame support. * DataSource and DataFrame implementation for Ignite SQL Tables. * IgniteCatalog implementation. * Some examples provided. *

[GitHub] ignite pull request #2743: IGNITE-6445_txLocksInfo

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/2743 IGNITE-6445_txLocksInfo You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite IGNITE-6445_txLocksInfo Alternatively you can

Integration of Spark and Ignite. Prototype.

Hello, guys. Currently, I’m working on integration between Spark and Ignite [1]. For now, I implement following: * Ignite DataSource implementation(IgniteRelationProvider) * DataFrame support for Ignite SQL table. * IgniteCatalog implementation for a transparent resolving of ignites

Re: Future of Ignite transactions

Dima, Becuase if you take any pair of our concurrency/isolation modes, you will not find anything similar in SQL. The main problem is that there is no "OPTIMISTIC" or "PESSIMISTIC" in SQL world. All reads are "optimistic", but can be converted to "perssimistic" optionally, and all writes are

[jira] [Created] (IGNITE-6496) Client node does not reconnect to server node when the latter is restarted.

Vyacheslav Koptilin created IGNITE-6496: --- Summary: Client node does not reconnect to server node when the latter is restarted. Key: IGNITE-6496 URL: https://issues.apache.org/jira/browse/IGNITE-6496

[jira] [Created] (IGNITE-6497) Broken tests in ignite-2.1.5

Yury Babak created IGNITE-6497: -- Summary: Broken tests in ignite-2.1.5 Key: IGNITE-6497 URL: https://issues.apache.org/jira/browse/IGNITE-6497 Project: Ignite Issue Type: Bug

Re: Future of Ignite transactions

Folks, Sorry for late reply. I had a chat with several Ignite veterans today. We tried to design transactional SQL for Ignite. One of our questions was how to align SQL transactions with current Ignite transactions. And we failed. And then we came to conclusion that current transaction API is

[GitHub] ignite pull request #2744: IGNITE-6444: Validate that copyOnRead flag is con...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/2744 IGNITE-6444: Validate that copyOnRead flag is configured with on-heap cache enabled. You can merge this pull request into a Git repository by running: $ git pull

Re: Persistence per memory policy configuration

Dima, let's finalize the design first. As I understand, we are happy with idea to merge MemoryConfiguration and PersistentStoreConfiguration into something what I called DataConfiguration, and to rename MemoryPolicyConfiguration to DataRegionConfiguration. The only outstanding qurestion is

[GitHub] ignite pull request #2425: IGNITE-5736 Add test of backward-compatibility

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/2425 ---

[jira] [Created] (IGNITE-6492) .NET: Tests: Task.Wait should always include a timeout

Pavel Tupitsyn created IGNITE-6492: -- Summary: .NET: Tests: Task.Wait should always include a timeout Key: IGNITE-6492 URL: https://issues.apache.org/jira/browse/IGNITE-6492 Project: Ignite

[jira] [Created] (IGNITE-6493) IgnitePdsWalTlbTest.testWalDirectOutOfMemory() hangs

Dmitriy Govorukhin created IGNITE-6493: -- Summary: IgnitePdsWalTlbTest.testWalDirectOutOfMemory() hangs Key: IGNITE-6493 URL: https://issues.apache.org/jira/browse/IGNITE-6493 Project: Ignite

[GitHub] ignite pull request #2738: IGNITE-6493 incorrect usage dataStreamer, must be...

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/2738 IGNITE-6493 incorrect usage dataStreamer, must be in try-with-resource You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2729: IGNITE-6486 .NET: Update IsActiveOnStart document...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2729 ---

[GitHub] ignite pull request #2727: IGNITE-6249 .NET: IgniteConfiguration.ConsistentI...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2727 ---

[jira] [Created] (IGNITE-6491) Race in TopologyValidator.validate() and EVT_NODE_LEFT listener calls (split-brain activator)

Alexandr Kuramshin created IGNITE-6491: -- Summary: Race in TopologyValidator.validate() and EVT_NODE_LEFT listener calls (split-brain activator) Key: IGNITE-6491 URL:

Re: Persistence per memory policy configuration

Guys, I suggest we finalize the configuration changes in the original ticket then: https://issues.apache.org/jira/browse/IGNITE-6030 and proceed with the changes. 2017-09-23 17:08 GMT+03:00 Dmitriy Setrakyan : > Can we specify what metrics will look like? I think we

Apache Ignite 2.3 release

Igniters, We already fixed 300+ tickets since AI 2.1.0 release. These tickets include a lot of new features (namely, SQL-related) and usability improvements. Not to say dozens of important bug fixes. I propose to start planning of AI 2.3.0 release. I think we can deliver it in a month as follows:

Re: Persistence per memory policy configuration

Vladimir, Can you please add the configuration example in the ticket? D. On Mon, Sep 25, 2017 at 12:20 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Guys, > > I suggest we finalize the configuration changes in the original ticket > then: