[jira] [Created] (IGNITE-3594) ODBC: Add connection properties to support distributed joins.

Vladimir Ozerov created IGNITE-3594: --- Summary: ODBC: Add connection properties to support distributed joins. Key: IGNITE-3594 URL: https://issues.apache.org/jira/browse/IGNITE-3594 Project: Ignite

Re: Apache Ignite - New Release

On Wed, Jul 27, 2016 at 4:00 AM, Semyon Boikov wrote: > Dmitry, all Ignite features are always thoroughly tested =) > True, completely forgot about it :) > I created branch ignite-1.7.0. > > On Wed, Jul 27, 2016 at 9:32 AM, Dmitriy Setrakyan >

Re: Batch support in Cassandra store

Hi Luiz, Logged batches is not the solution to achieve atomic view of your Ignite transaction changes in Cassandra. The problem with logged batches(aka atomic) is they guarantees that if any part of the batch succeeds, all of it will, no other transactional enforcement is done at the batch

Re: Batch support in Cassandra store

Hi Igor, Does it make sense for you using logged batches to guarantee atomicity in Cassandra in cases we are doing a cross cache transaction operation? Luiz -- Luiz Felipe Trevisan On Wed, Jul 27, 2016 at 2:05 AM, Dmitriy Setrakyan wrote: > I am very confused still.

Re: Enums and SQL queries

Sorry, Sergi. What I meant is to file a ticket with the design you suggested Dmitriy > On Jul 27, 2016, at 9:18 AM, Sergi Vladykin wrote: > > I don't see how this can work to file a ticket, could you please give more > details? > > Sergi > > 2016-07-27 15:50

Re: IGNITE-2294 implementation details

Sergi, I've made changes to the API according to your valuable recommendations, thank you very much for giving them. Please refer to PR to see current state of the work. Will surely look into ODBC, .NET and Visor. Though they will most likely have to support a new feature rather than considerably

Re: Ignite 2.0 tasks/roadmap

On Wed, Jul 27, 2016 at 11:36 AM, Yakov Zhdanov wrote: > Guys, I think we can also split event notification for user listeners and > internal system listeners. I have been seeing a lot of issues caused by > some heavy or blocking operations in user-defined listeners. This

[GitHub] ignite pull request #903: IGNITE-3593 .NET: Fix IgniteConfiguration.WorkDire...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/903 IGNITE-3593 .NET: Fix IgniteConfiguration.WorkDirectory having no effect You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

Re: Ignite 2.0 tasks/roadmap

Guys, I think we can also split event notification for user listeners and internal system listeners. I have been seeing a lot of issues caused by some heavy or blocking operations in user-defined listeners. This may block internal component notification (e.g. on discovery event) causing topology

[GitHub] ignite pull request #902: GG-11360 Merged IGNITE-2680 to ignite-1.6.3.

GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/902 GG-11360 Merged IGNITE-2680 to ignite-1.6.3. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ascherbakoff/ignite ignite-gg-11360

Re: Enums and SQL queries

I don't see how this can work to file a ticket, could you please give more details? Sergi 2016-07-27 15:50 GMT+03:00 Dmitriy Setrakyan : > Sergi, I still thinks my solution works or can be made to work. In the > example you provided, you can choose to return either String

Re: Enums and SQL queries

Sergi, I still thinks my solution works or can be made to work. In the example you provided, you can choose to return either String or Enum as the query result. However, this is not a clean solution, I agree, but could be a quick one. I don't mind breaking compatibility on this issue, given that

[jira] [Created] (IGNITE-3593) .NET: IgniteConfiguration.WorkDirectory has no effect

Pavel Tupitsyn created IGNITE-3593: -- Summary: .NET: IgniteConfiguration.WorkDirectory has no effect Key: IGNITE-3593 URL: https://issues.apache.org/jira/browse/IGNITE-3593 Project: Ignite

Re: Data compression in Ignite 2.0

FYI, I created issue for Ignite 2.0: https://issues.apache.org/jira/browse/IGNITE-3592 Thanks! On Wed, Jul 27, 2016 at 2:36 PM, Sergi Vladykin wrote: > Nikita, > > I agree with Andrey, HANA is a bad comparison to Ignite in this respect. I > did not find any evidence

[jira] [Created] (IGNITE-3592) Provide some kind of pluggable compression SPI support

Alexey Kuznetsov created IGNITE-3592: Summary: Provide some kind of pluggable compression SPI support Key: IGNITE-3592 URL: https://issues.apache.org/jira/browse/IGNITE-3592 Project: Ignite

Re: IGNITE-2294 implementation details

Please don't forget about ODBC, .NET and Visor. They all have to work in the same way. Sergi 2016-07-27 14:15 GMT+03:00 Alexander Paschenko < alexander.a.pasche...@gmail.com>: > OK, I've found that bold cast to QueryCursor in IgniteCacheProxy > and had a look at how SqlFieldsQuery is used in

Re: IGNITE-2294 implementation details

OK, I've found that bold cast to QueryCursor in IgniteCacheProxy and had a look at how SqlFieldsQuery is used in JDBC driver. Thanks. - Alex 2016-07-27 13:02 GMT+03:00 Sergi Vladykin : > Where did you see R in SqlFieldsQuery? > > Sergi > > 2016-07-27 12:59 GMT+03:00

[GitHub] ignite pull request #901: IGNITE-1084 fixed issue broken HibernateL2CacheSel...

GitHub user mwadhwa opened a pull request: https://github.com/apache/ignite/pull/901 IGNITE-1084 fixed issue broken HibernateL2CacheSelfTest#testNaturalI… …dCache() You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #900: IGNITE-3561 .NET: DistributedJoins property in Sql...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/900 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: IGNITE-2294 implementation details

Where did you see R in SqlFieldsQuery? Sergi 2016-07-27 12:59 GMT+03:00 Alexander Paschenko < alexander.a.pasche...@gmail.com>: > Sergi, > > But current signature of query() method returns not just some > iterator, but rather iterator of R which is type param of Query - > i.e., we won't be able

Re: IGNITE-2294 implementation details

Sergi, But current signature of query() method returns not just some iterator, but rather iterator of R which is type param of Query - i.e., we won't be able to return an int inside a QueryCursor. At least without API change (signature of query() method will have to be changed to drop

Re: IGNITE-2294 implementation details

Exactly. This will allow our Jdbc driver to work transparently. Sergi 2016-07-27 12:40 GMT+03:00 Alexander Paschenko < alexander.a.pasche...@gmail.com>: > Sergi, > > You wrote: > > I'd prefer to return the same information, so it will not be empty > > Do you mean return iterator with single

Re: IGNITE-2294 implementation details

Sergi, You wrote: > I'd prefer to return the same information, so it will not be empty Do you mean return iterator with single element that denotes number of rows? Dmitriy, You wrote: > What is the ticket number for this. Is the new API documented there? Overall issue number is 2294. There's

[GitHub] ignite pull request #895: IGNITE-3323 Use maven dependencies for Jetbrains a...

Github user jayho closed the pull request at: https://github.com/apache/ignite/pull/895 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #900: IGNITE-3561 .NET: DistributedJoins property in Sql...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/900 IGNITE-3561 .NET: DistributedJoins property in SqlQuery & SqlFieldsQuery - improve API and tests You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-3591) .NET: Self-joins do not work in LINQ

Pavel Tupitsyn created IGNITE-3591: -- Summary: .NET: Self-joins do not work in LINQ Key: IGNITE-3591 URL: https://issues.apache.org/jira/browse/IGNITE-3591 Project: Ignite Issue Type: Bug

Re: Apache Ignite - New Release

Dmitry, all Ignite features are always thoroughly tested =) I created branch ignite-1.7.0. On Wed, Jul 27, 2016 at 9:32 AM, Dmitriy Setrakyan wrote: > On Wed, Jul 27, 2016 at 2:29 AM, Semyon Boikov > wrote: > > > Sure Dmitry, we will run tests with

Re: Data compression in Ignite 2.0

Nikita, I agree with Andrey, HANA is a bad comparison to Ignite in this respect. I did not find any evidence on the internet that their row store is very efficient with compression. It was always about column store. Alexey, As for DB2, can you check what exactly, when and how it compresses and

Re: IgniteConfiguration.toXml()

So, no objections for adding this in .NET? Another important use case is migrating from Spring XML (the only option in 1.5) to .NET XML (1.6+): instead of rewriting config by hand, users can call ignite.GetConfigurarion().ToXml() and copy the result. On Tue, Jul 26, 2016 at 11:17 AM, Alexey

[jira] [Created] (IGNITE-3590) Create test and first simple implementation of secondary file system.

Dmitry Karachentsev created IGNITE-3590: --- Summary: Create test and first simple implementation of secondary file system. Key: IGNITE-3590 URL: https://issues.apache.org/jira/browse/IGNITE-3590

Re: Data compression in Ignite 2.0

Hi I add Redis as a sample of memory compression strategy http://labs.octivi.com/how-we-cut-down-memory-usage-by-82/ http://redis.io/topics/memory-optimization Regards S DIAZ 2016-07-27 8:24 GMT+02:00 Alexey Kuznetsov : > Nikita, > > That was my intention: "we may

Re: Enums and SQL queries

Nope. This will not work. Because take for example the following query: select my_enum_field from my_table where my_enum_field = 'BLA' Field well be evaluated only once here, but it must be a Sting and Enum at the same time. Probably we could contribute to H2 `User defined value types` and

Re: Apache Ignite - New Release

On Wed, Jul 27, 2016 at 2:29 AM, Semyon Boikov wrote: > Sure Dmitry, we will run tests with large data set. > > Regarding 1.7. release: If there are no objections I'm going to cut off 1.7 > branch and start prepare it for release. > In my opinion this is a great addition

[jira] [Created] (IGNITE-3589) Add support for distributed joins to SQL screen on Web Console

Alexey Kuznetsov created IGNITE-3589: Summary: Add support for distributed joins to SQL screen on Web Console Key: IGNITE-3589 URL: https://issues.apache.org/jira/browse/IGNITE-3589 Project:

Re: Data compression in Ignite 2.0

Nikita, That was my intention: "we may need to provide a better facility to inject user's logic here..." Andrey, About compression, once again - DB2 is a row-based DB and they can compress :) On Wed, Jul 27, 2016 at 12:56 PM, Nikita Ivanov wrote: > Very good points

Re: Enums and SQL queries

Hm... I would prefer to find a way to handle Enums automatically. In case if user expects a String, can we catch an exception and do automatic conversion at that time? In this case, we could catch the exception once and remember the decision. Will something like this work? D. On Tue, Jul 26,

Re: IGNITE-2294 implementation details

What is the ticket number for this. Is the new API documented there? On Tue, Jul 26, 2016 at 11:36 AM, Sergi Vladykin wrote: > I don't see anything ugly in empty iterator, sorry if I insulted your taste > of beauty. > > If you will take a look at Jdbc, you will see

Re: Apache Ignite - New Release

On Wed, Jul 27, 2016 at 2:09 AM, Semyon Boikov wrote: > Regarding distributed join testsing: we added tests verifying correct join > behavior and correct execution plan generation for various SQL queries, > tests for joins for various cache types (different number of

Re: Apache Ignite - New Release

Regarding distributed join testsing: we added tests verifying correct join behavior and correct execution plan generation for various SQL queries, tests for joins for various cache types (different number of backups, partitioned/replicated), there are tests verifying correct distributed joins

Re: Batch support in Cassandra store

I am very confused still. Ilya, can you please explain what happens in Cassandra if user calls IgniteCache.putAll(...) method? In Ignite, if putAll(...) is called, Ignite will make the best effort to execute the update as a batch, in which case the performance is better. What is the analogy in