Re: [VOTE] Apache Ignite 2.2.0 RC1

How could we miss these binaries? Isn't the release procedure automated ODBC installers creation? I thought a smoke-testing is done for a final release deliverable. Restarting the vote I guess? -- Denis On Tuesday, September 12, 2017, Igor Sapego wrote: > Wait, there is no

[GitHub] ignite pull request #2652: IGNITE-6260 rename setDistributedJoins to setNonC...

GitHub user vk23 reopened a pull request: https://github.com/apache/ignite/pull/2652 IGNITE-6260 rename setDistributedJoins to setNonCollocatedJoins 1. SqlQuery, SqlFieldsQuery: old methods deprecated, new ones added. 2. All internal usages of the deprecated methods are replaced

[GitHub] ignite pull request #2652: IGNITE-6260 rename setDistributedJoins to setNonC...

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

Re: How much memory/disc I need to keep my data?

Agree with Vladimir - the second option seems to be more interesting. Guys, can we also give recommendations to user on building more effective data model? For example, can we detect dates in string or indexes on boolean fields that most probably have very low selectivity or indexed field which

[jira] [Created] (IGNITE-6363) Web console: Add refresh SVG icon to icon set

Vasiliy Sisko created IGNITE-6363: - Summary: Web console: Add refresh SVG icon to icon set Key: IGNITE-6363 URL: https://issues.apache.org/jira/browse/IGNITE-6363 Project: Ignite Issue Type:

[GitHub] ignite pull request #2653: IGNITE-6347: Read unsigned short in GridDhtPartit...

GitHub user mlipkovich opened a pull request: https://github.com/apache/ignite/pull/2653 IGNITE-6347: Read unsigned short in GridDhtPartitionMap You can merge this pull request into a Git repository by running: $ git pull https://github.com/mlipkovich/ignite ignite-6347

Re: Persistence per memory policy configuration

I would go for PersistentMemoryPolicyConfiguration way if it will be expanded by storage related settings furthers. For instance, from the discussion on @user I see a raising demand for the storage maximum size. If it’s reached the data will be evicted from there too. Just as an example. —

Re: AffinityKeyMapper alternatives

Dmitry, IMO, it's actually pretty typical for data grid use cases where affinity key is usually provided as part of key itself, i.e. after cache creation. In vast majority of cases I've seen, this is done via very popular @AffinityKeyMapped annotation. My only point is that the annotation can't

Re: Web Sessions not considered valid by our RequestWrapper - FIX

Ilya, I see you have a fully-pledged application to test the scenario. Is it possible to include it (probably simplified a bit) into our tests suites so that it runs periodically? This will not only verify this particular fix, but also prevent us from other issues that may occur. -Val On Tue,

Re: guard() and checkClusterState() checks in Ignite Kernal

Is there a ticket for this change? On Tue, Sep 12, 2017 at 4:25 AM, Ilya Kasnacheev wrote: > Rehi, > > After some discussions https://github.com/apache/ignite/pull/2526 seems to > have correct changeset that covers two methods which seem to have been > overlooked

Re: sql documentation

Thanks Sergey, I think we should add SQL Syntax section on the left. Also, please let us know when we can proof read it. I would like to fix some phrasing on the page. On Tue, Sep 12, 2017 at 8:26 AM, Serge Puchnin wrote: > I've added a page for SQL language, create

Re: New thin client and interfaces/facades

Vladimir, I disagree. We already have client mode which support the full Ignite API. Here we are talking about the new client binary protocol. To my knowledge, the following APIs can be implemented over the new binary protocol: - JDBC - ODBC - REST - .NET Thin All these protocols are already

[GitHub] ignite pull request #2652: IGNITE-6260: rename setDistributedJoins to setNon...

GitHub user vk23 opened a pull request: https://github.com/apache/ignite/pull/2652 IGNITE-6260: rename setDistributedJoins to setNonCollocatedJoins 1. SqlQuery, SqlFieldsQuery: old methods deprecated, new ones added. 2. All internal usages of the deprecated methods are replaced

[GitHub] ignite pull request #2651: Ignite-gg12701-

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2651 Ignite-gg12701- for tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12701 Alternatively you can

[GitHub] ignite pull request #2650: Ignite-gg-12701

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

[GitHub] ignite pull request #2650: Ignite-gg-12701

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2650 Ignite-gg-12701 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12701 Alternatively you can review and

Re: Persistence per memory policy configuration

While we are contemplating the best way to introduce this feature I have a side note to consider. Can the user enable CacheStore (RDBMS, Cassandra) for caches that are not persisted in Ignite Persistence? That’s one of the use cases I hear a lot about - some of the caches need persisted in

Re: New thin client and interfaces/facades

+1 one for the first approach. The users will start with a documentation page where we can define in a table format the scope of supported APIs. — Denis > On Sep 12, 2017, at 3:06 AM, Pavel Tupitsyn wrote: > > I prefer the first approach. > Users can easily switch to

[jira] [Created] (IGNITE-6361) Add Meta descriptions on Ignite website pages

Prachi Garg created IGNITE-6361: --- Summary: Add Meta descriptions on Ignite website pages Key: IGNITE-6361 URL: https://issues.apache.org/jira/browse/IGNITE-6361 Project: Ignite Issue Type:

[GitHub] ignite pull request #2649: Ignite-gg-12767s

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2649 Ignite-gg-12767s for test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12767 Alternatively you can

Re: [VOTE] Apache Ignite 2.2.0 RC1

Wait, there is no platforms\cpp\bin directory with odbc installers in binary release. Can someone double-check? Best Regards, Igor On Tue, Sep 12, 2017 at 7:44 PM, Igor Sapego wrote: > +1 > > Checked: > - Building of x86 and amd64 versions of C++ binaries. > - Building of

Re: ContinuousQueryWithTransformer implementation questions - 2

I meant "It is much better *than* extend*ing* confusing behavior *of *already confusing and overengineered API." On Tue, Sep 12, 2017 at 7:35 PM, Vladimir Ozerov wrote: > Nikolay, > > Public API is the face of our product. We cannot and do not want to change > it in a

Re: How much memory/disc I need to keep my data?

Another important point is that size estimation is typically used to estimate costs. We are talking about real money of our users. Inaccurate estimates might lead wrong decisions and lost money. We should take this feature very serious. On Tue, Sep 12, 2017 at 7:40 PM, Vladimir Ozerov

Re: [VOTE] Apache Ignite 2.2.0 RC1

+1 Checked: - Building of x86 and amd64 versions of C++ binaries. - Building of x86 and amd64 versions of ODBC. - C++ examples. Best Regards, Igor On Tue, Sep 12, 2017 at 6:16 PM, Andrey Gura wrote: > +1 > > On Tue, Sep 12, 2017 at 6:09 PM, Kozlov Maxim

Re: How much memory/disc I need to keep my data?

We should keep in mind two very important things. First, binary object format is not storage format by design. Second, real space consumption heavily depend on configuration (backups, page size, indexes, compression, etc.). For this reason by estimating sizes of binary objects user would estimate

Re: ContinuousQueryWithTransformer implementation questions - 2

Nikolay, Public API is the face of our product. We cannot and do not want to change it in a rush. This ticket was in a backlog for more than 2 years. It is not a big problem if we spend additional week or month for API design. It is much better to extend confusing behavior on already confusing

Re: ContinuousQueryWithTransformer implementation questions - 2

Dima, We definitely can have factories if we want. On Tue, Sep 12, 2017 at 5:55 PM, Dmitriy Setrakyan wrote: > Vladimir, are their factories for the proposed listeners? > > On Tue, Sep 12, 2017 at 7:52 AM, Alexey Goncharuk < > alexey.goncha...@gmail.com> wrote: > > >

Re: ContinuousQueryWithTransformer implementation questions - 2

Alex, The source of our confusion in current API is that we called "filter" what actually should be "listener". I propose to set has the simplest API possible. Note that CacheEntryListener is a part of jcache API. Call of this method will set passed listener on remote nodes. Nothing more. UUID

How much memory/disc I need to keep my data?

Igniters, Since we're developing some kind of storage system it's pretty interesting how effectively it stores data. I propose to develop some Estimator allows to count how much space is needed to keep any data. For example: 1) You have classes A,B and C with known fields and data distribution

Re: Web Sessions not considered valid by our RequestWrapper - FIX

Val, can you please help? --Yakov 2017-09-12 14:30 GMT+03:00 Ilya Kasnacheev : > Hello Igniters, > > It came to our attention that our handling of Web Sessions is inconsistent: > https://stackoverflow.com/questions/45648884/apache- > ignite-spring-secutiry-error > >

[GitHub] ignite pull request #2648: ignite-4931 tests reworked

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2648 ignite-4931 tests reworked You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-4931 Alternatively you can review and apply

Re: ContinuousQueryWithTransformer implementation questions - 2

Vova > I propose to deprecate current continuous queries and develop new API. > This should not break anything. If the community agrees that *whole* continuous query API is bad - it OK. Let's develop new API. But developing new public API and implementing it is a very long process. One can see

[jira] [Created] (IGNITE-6360) NPE occurs if object with null indexed field is added

Mikhail Cherkasov created IGNITE-6360: - Summary: NPE occurs if object with null indexed field is added Key: IGNITE-6360 URL: https://issues.apache.org/jira/browse/IGNITE-6360 Project: Ignite

[GitHub] ignite pull request #2647: IGNITE-6355 Calculating cache size during cache s...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2647 IGNITE-6355 Calculating cache size during cache stop sporadically fails with ClusterGroupEmptyCheckedException You can merge this pull request into a Git repository by running: $ git pull

Re: sql documentation

I would suggest to change second "SQL" topic to following SQL statement syntax - DML - SELECT ... - DDL - CREATE TABLE - DROP TABLE - ALTER TABLE - CREATE INDEX - ANSI 99 compliance On Tue, Sep 12, 2017 at 6:26 PM, Serge Puchnin

Re: sql documentation

I've added a page for SQL language, create index statement and Upper function as an example for the new format: https://apacheignite-sql.readme.io/v2.1/docs/create-index For me, it'd be OK to add a separate page for each SQL statement. BR, Serge On Sat, 9 Sep 2017 at 02:19, Denis Magda

[GitHub] ignite pull request #2615: Ignite-gg-12695

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

Re: [VOTE] Apache Ignite 2.2.0 RC1

+1 On Tue, Sep 12, 2017 at 6:09 PM, Kozlov Maxim wrote: > +1 > >> 12 сент. 2017 г., в 17:36, Sergey Kozlov написал(а): >> >> +1 >> >> >> >> On Tue, Sep 12, 2017 at 5:21 PM, Vladimir Ozerov >> wrote: >> >>> +1 (binding) >>> >>>

Re: ContinuousQueryWithTransformer implementation questions - 2

Vladimir, are their factories for the proposed listeners? On Tue, Sep 12, 2017 at 7:52 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Vladimir, > > Can you please clarify how the proposed API will work? > > My opinion is that our query API is big piece of ... you know, especially >

Re: Persistence per memory policy configuration

Yakov, The default=true will be used only if the PersistentStoreConfiguration is set in the IgniteConfiguration, this is done only to maintain configuration compatibility. A user is allowed to use persisted and in-memory caches, he will be only forced to put them into separate memory policies.

Re: ContinuousQueryWithTransformer implementation questions - 2

Vladimir, Can you please clarify how the proposed API will work? My opinion is that our query API is big piece of ... you know, especially > ContinuousQuery. A lot of concepts and features are mixed in a single > entity, what makes it hard to understand and use. Let's finally deprecate >

[jira] [Created] (IGNITE-6359) .NET: Improve tests for object graphs and loops

Pavel Tupitsyn created IGNITE-6359: -- Summary: .NET: Improve tests for object graphs and loops Key: IGNITE-6359 URL: https://issues.apache.org/jira/browse/IGNITE-6359 Project: Ignite Issue

[GitHub] ignite pull request #2646: IGNITE-6330: Implemented closing of ODBC and JDBC...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/2646 IGNITE-6330: Implemented closing of ODBC and JDBC cursors on client disconnect You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2645: IGNITE-6354 .NET: Fix DataStreamer with complex o...

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

Re: ContinuousQueryWithTransformer implementation questions - 2

Yakov, I propose to deprecate current continuous queries and develop new API. This should not break anything. Adding transformers on top of current API will make it total mess. On Tue, Sep 12, 2017 at 5:39 PM, Николай Ижиков wrote: > Yakov. > > > 2. In a new class we

Re: ContinuousQueryWithTransformer implementation questions - 2

Yakov. > 2. In a new class we still have initial query which uses types which is questionable. After some discussion with a colleague, I think I got your point. If I understand your question right: Why does someone want to execute an initial query that returns ? If one use

Re: [VOTE] Apache Ignite 2.2.0 RC1

+1 On Tue, Sep 12, 2017 at 5:21 PM, Vladimir Ozerov wrote: > +1 (binding) > > On Tue, Sep 12, 2017 at 4:24 PM, Pavel Tupitsyn > wrote: > > > +1 (binding) > > > > Checked: > > - Build from sources (Java, .NET) > > - Examples (.NET) > > > > On Tue,

Re: ContinuousQueryWithTransformer implementation questions - 2

Agree with Vladimir. However, this will break API compatibility. So, at this point this is impossible. --Yakov

Re: [VOTE] Apache Ignite 2.2.0 RC1

+1 (binding) On Tue, Sep 12, 2017 at 4:24 PM, Pavel Tupitsyn wrote: > +1 (binding) > > Checked: > - Build from sources (Java, .NET) > - Examples (.NET) > > On Tue, Sep 12, 2017 at 11:40 AM, Ilya Suntsov > wrote: > > > +1 > > > > Checked: > > > >

[jira] [Created] (IGNITE-6358) JDBC thick: support multiple SQL statements

Vladimir Ozerov created IGNITE-6358: --- Summary: JDBC thick: support multiple SQL statements Key: IGNITE-6358 URL: https://issues.apache.org/jira/browse/IGNITE-6358 Project: Ignite Issue

[jira] [Created] (IGNITE-6357) ODBC: support multiple SQL statements

Vladimir Ozerov created IGNITE-6357: --- Summary: ODBC: support multiple SQL statements Key: IGNITE-6357 URL: https://issues.apache.org/jira/browse/IGNITE-6357 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #2638: IGNITE-6151: Impemented getting and setting of th...

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

[GitHub] ignite pull request #2341: IGNITE-5648: SQL: Added support for NOT NULL cons...

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

[jira] [Created] (IGNITE-6356) Signed overflow when reading partition greater than Short.MAX_VALUE

Alexey Goncharuk created IGNITE-6356: Summary: Signed overflow when reading partition greater than Short.MAX_VALUE Key: IGNITE-6356 URL: https://issues.apache.org/jira/browse/IGNITE-6356 Project:

[jira] [Created] (IGNITE-6355) Calculating cache size during cache stop sporadically fails with ClusterGroupEmptyCheckedException

Ivan Rakov created IGNITE-6355: -- Summary: Calculating cache size during cache stop sporadically fails with ClusterGroupEmptyCheckedException Key: IGNITE-6355 URL: https://issues.apache.org/jira/browse/IGNITE-6355

Re: [VOTE] Apache Ignite 2.2.0 RC1

+1 (binding) Checked: - Build from sources (Java, .NET) - Examples (.NET) On Tue, Sep 12, 2017 at 11:40 AM, Ilya Suntsov wrote: > +1 > > Checked: > >- Build from sources >- Build examples (ML profile enabled) >- Checked md5, sha512 and signs > > > 2017-09-12

[GitHub] ignite pull request #2645: IGNITE-6354 .NET: Fix DataStreamer with complex o...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/2645 IGNITE-6354 .NET: Fix DataStreamer with complex object graphs You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-6354

[GitHub] ignite pull request #2594: IGNITE-5145 Support multiple service deployment i...

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

[GitHub] ignite pull request #2571: IGNITE-6214 resolve problem with concurrent metad...

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

Re: ContinuousQueryWithTransformer implementation questions - 2

Hello, Vladimir. class ContinuousQueryCacheEntryListener implements CacheEntryListener { ContinuousQueryRemoteFilter rmtFilter; ContinuousQueryRemoteTransformer rmtTransformer; ContinuousQueryLocalCallback locCb; } I think class you proposed should be separated in two because of

Re: ContinuousQueryWithTransformer implementation questions - 2

My opinion is that our query API is big piece of ... you know, especially ContinuousQuery. A lot of concepts and features are mixed in a single entity, what makes it hard to understand and use. Let's finally deprecate ContinuousQuery and design nice and consistent API. E.g.: interface IgniteCache

[GitHub] ignite pull request #2644: IGNITE-6284: Added compute withNoResultCache meth...

GitHub user mlipkovich opened a pull request: https://github.com/apache/ignite/pull/2644 IGNITE-6284: Added compute withNoResultCache method You can merge this pull request into a Git repository by running: $ git pull https://github.com/mlipkovich/ignite ignite-6284

Re: How to configure new thin client connector on the server?

In that case, ClientConnectorConfiguration seems like a good name. Can the migration be done in such a way that the old configuration will be deprecated, but still work? D. On Tue, Sep 12, 2017 at 2:34 AM, Vladimir Ozerov wrote: > Dima, > > Yes. > > On Tue, Sep 12, 2017

[jira] [Created] (IGNITE-6354) .NET: DataStreamer does not work with complex object graphs

Pavel Tupitsyn created IGNITE-6354: -- Summary: .NET: DataStreamer does not work with complex object graphs Key: IGNITE-6354 URL: https://issues.apache.org/jira/browse/IGNITE-6354 Project: Ignite

Re: ContinuousQueryWithTransformer implementation questions - 2

Dmitry, can you please take a look at public API change. Ticket - https://issues.apache.org/jira/browse/IGNITE-425 PR - https://github.com/apache/ignite/pull/2372 Issues: 1. Do you see any other option other than creating separate class? As for me I don't. 2. In a new class we still have initial

[jira] [Created] (IGNITE-6353) Integrate mvcc support in scan query protocol

Semen Boikov created IGNITE-6353: Summary: Integrate mvcc support in scan query protocol Key: IGNITE-6353 URL: https://issues.apache.org/jira/browse/IGNITE-6353 Project: Ignite Issue Type:

[GitHub] ignite pull request #2643: Ignite-1.7.16

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2643 Ignite-1.7.16 for tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.7.16 Alternatively you can review

[jira] [Created] (IGNITE-6352) ignite-indexing is not compatible to OSGI

Mikhail Cherkasov created IGNITE-6352: - Summary: ignite-indexing is not compatible to OSGI Key: IGNITE-6352 URL: https://issues.apache.org/jira/browse/IGNITE-6352 Project: Ignite Issue

[GitHub] ignite pull request #2616: Ignite-gg-12707

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

Web Sessions not considered valid by our RequestWrapper - FIX

Hello Igniters, It came to our attention that our handling of Web Sessions is inconsistent: https://stackoverflow.com/questions/45648884/apache-ignite-spring-secutiry-error I've filed https://issues.apache.org/jira/browse/IGNITE-6070 and fixed the issue in

Re: guard() and checkClusterState() checks in Ignite Kernal

Rehi, After some discussions https://github.com/apache/ignite/pull/2526 seems to have correct changeset that covers two methods which seem to have been overlooked before. It's already reviewed by another contributor, please merge it into master you seem fit. Regards, Ilya. -- Ilya Kasnacheev

Re: Persistence per memory policy configuration

Agree that implicit actions are always source of issues of different kinds. Alex, having persistence enabled by default does not seem to be a good idea. >I think if we go with "persistence per cache" path, we must just enforce the correct configuration and let users configure the rest What do

Re: Persistence per memory policy configuration

This may work. But I do not like any implicit memory policy cloning because this will double the expected memory consumption and result in questions "why does my Ignite take 2x more memory when I enable persistence" from users. I think if we go with "persistence per cache" path, we must just

Re: Persistence per memory policy configuration

Can we leave the default policy as is, but clone it with persistence enabled on demand? E.g: - user starts Ignite with default config - createCache without persistence - use default policy - createCache with persistence - clone default policy with enabled persistence and some predefined postfix -

Re: New thin client and interfaces/facades

I prefer the first approach. Users can easily switch to client mode, run their code and see what works and what not. Second approach may require huge amount of refactoring to even try the client mode. And new users have to make a tough choice, because switching later is hard. As a middle ground

Re: Persistence per memory policy configuration

We surely can, but: * we should then have two configuration settings for default memory policy size (one in-memory and one persisted) * a user still may configure multiple custom memory policies. In this case, the requirement to have this flag the same in a memory policy is still valid, so a

[GitHub] ignite pull request #2642: Ignite gg 12755

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/2642 Ignite gg 12755 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12755 Alternatively you can review and

Re: Persistence per memory policy configuration

Alex, Can we have two default memory policies - one for in-memory and another one for persistence cases? On Tue, Sep 12, 2017 at 12:40 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > This is possible, but then if two caches belong to the same memory policy, > they must be both

New thin client and interfaces/facades

Igniters, We are developing new thin client. There are two approaches on how to design it's interfaces - either re-use existing Ignite interfaces, or define new. Both approaches has pros and cons *1) Re-use interfaces* This approach is used in Hazelcast. Both server and client share the same

Re: Persistence per memory policy configuration

This is possible, but then if two caches belong to the same memory policy, they must be both either persistence-enabled or persistence-disabled. We can add this validation, but I think this will lead to a greater confusion for a user. 2017-09-12 12:34 GMT+03:00 Pavel Tupitsyn

Re: Persistence per memory policy configuration

Agree with Vladimir. Currently we enable persistence cluster-wide by setting IgniteConfiguration.persistentStoreConfiguration. Ideally CacheConfiguration.persistenceEnabled should be the only setting I need to set. Thanks, Pavel On Tue, Sep 12, 2017 at 12:28 PM, Vladimir Ozerov

Re: How to configure new thin client connector on the server?

Dima, Yes. On Tue, Sep 12, 2017 at 1:50 AM, Dmitriy Setrakyan wrote: > In my opinion all clients, including JDBC, ODBC, and REST should be > implemented over the same protocol and we should not have the protocol mess > we have today. > > Vladimir, does your suggestion

Re: Persistence per memory policy configuration

As a user I would definitely prefer to control persistence through flag on cache configuration. I do not even want to know what "memory policy" is. E.g. CacheConfiguration.persistenceEnabled. On Tue, Sep 12, 2017 at 12:24 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Igniters, > >

Persistence per memory policy configuration

Igniters, I am currently reviewing a change allowing to enable persistence on a per-memory-policy basis (thanks to K. Dudkov!) and have a question regarding the changes in configuration. The suggested change is to add a flag "persistenceEnabled" (defaults to true) to the memory policy

[jira] [Created] (IGNITE-6350) SQL: Forbid NOT NULL constraints usage for a cache with configured read-through cache store

Sergey Kalashnikov created IGNITE-6350: -- Summary: SQL: Forbid NOT NULL constraints usage for a cache with configured read-through cache store Key: IGNITE-6350 URL:

Re: Start contributing to Apache Ignite

Thanks a lot Denis! Will try to do something useful Mikhail 2017-09-12 3:41 GMT+03:00 Denis Magda : > Mikhail, welcome! > > Granted you required permissions! Look forward to your contributions! > > — > Denis > > > On Sep 11, 2017, at 4:33 AM, Mikhail Lipkovich < >

[GitHub] ignite pull request #2631: IGNITE-6326 JDBC thin: statement type mismatch er...

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

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

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/2641 ignite-5960 continuous query entry update race fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite ignite-5960 Alternatively you

[jira] [Created] (IGNITE-6348) Web Console: Implement control for selecting and activating cluster

Alexey Kuznetsov created IGNITE-6348: Summary: Web Console: Implement control for selecting and activating cluster Key: IGNITE-6348 URL: https://issues.apache.org/jira/browse/IGNITE-6348 Project: