Re: Timeout for ordered message

If you send ordered messages to a node and listener on receiving side has not yet been added then timeout is still sufficient to clean up buffered messages. --Yakov 2017-01-10 23:36 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Yakov, > > I was actually asking about the publi

[jira] [Created] (IGNITE-4540) Ability to disable default H2 Indexing.

Andrew Mashenkov created IGNITE-4540: Summary: Ability to disable default H2 Indexing. Key: IGNITE-4540 URL: https://issues.apache.org/jira/browse/IGNITE-4540 Project: Ignite Issue Type:

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

Hi all I have a comment about release notes. Transactions deadlock detection was implemented in Apache Ignite 1.7. But this implementation is limited by pessimistic transactions only and doesn't support transactions on near caches. In Apache Ignite 1.8 release implemented deadlock detection that

[GitHub] ignite pull request #1420: Ignite 3543

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1420 Ignite 3543 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3543 Alternatively you can review and apply the

Re: SQL query CPU utilization too low.

I've done with splitting indices: distributed joins has been fixed, issues with prepared statements cache has been disappear. Ticket Ignite-4106 [1] is ready for review. [1] https://issues.apache.org/jira/browse/IGNITE-4106 On Mon, Dec 5, 2016 at 3:16 PM, Sergi Vladykin wrote: > I'd prefer to a

[GitHub] ignite pull request #1349: ignite 4026

Github user ntikhonov closed the pull request at: https://github.com/apache/ignite/pull/1349 --- 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: SQL query collocated flag

It means exactly that: more effective plan. If we know in advance that entries will be grouped by colocated field, then we can avoid grouping on reduce side. If they are grouped by non-colocated field and the flag is set, then the plan will be invalid and user will get wrong result. I'm not sure ho

[GitHub] ignite pull request #1421: Ignite 3542

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1421 Ignite 3542 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3542 Alternatively you can review and apply the

[GitHub] ignite pull request #1422: IGNITE-3837: ODBC: Support for CONVERT function e...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/1422 IGNITE-3837: ODBC: Support for CONVERT function escape sequence You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ign

Allow distributed SQL query execution over explicit set of partitions

Guys, I've just submitted a PR for https://issues.apache.org/jira/browse/IGNITE-4523. Please review API changes while waiting for TC results. -- Best regards, Alexei Scherbakov

Re: Allow distributed SQL query execution over explicit set of partitions

Alexey, I am not sure I am seeing the API changes documented in the ticket. Can you please either document them or add GIT links for the new classes? D. On Wed, Jan 11, 2017 at 9:29 AM, Alexei Scherbakov < alexey.scherbak...@gmail.com> wrote: > Guys, > > I've just submitted a PR for > https://i

DDL implementation details

Hello Igniters, I would like to start discussion about implementation of SQL DDL commands. At the first stage, the most important ones seem to be CREATE TABLE (that will obviously correspond to creation of a cache) and CREATE INDEX. Regarding first one: SQL command for CREATE TABLE does not cont

Re: DDL implementation details

Hi, Alex! As far as I know most RDBMS allow something like: create table t1 (id integer primary key, ) How about to take as key field that marked as "primary key"? As of atomicity and replication - I think it is a cache properties and with create table we will create "types" in cache. No? I t

Re: DDL implementation details

I believe custom synthax and parsing is a *must* for us, as well as for any distributed database. At the very least we need to specify affinity key column somehow. Any cache property can be specified at the very end of table definition. Key columns can be determined as the ones with PRIMARY KEY con

Re: DDL implementation details

Hi I suppose we should put any ignite cache properties as additional non-standard attributes after CREATE TABLE () clause as it does Postgress, MySQL and other RDBMS. Take a look on CREATE TABLE with using TABLESPACE (Postgess) or for CREATE TABLE with using PARTITIONS (MySQL). On Wed, Jan 11

Re: Timeout for ordered message

Yakov, So you confirm that my understanding is correct and JavaDoc is wrong, right? As for 'no listener' scenario, that's a good point, but it should be applicable to unordered messages as well then. The most confusing part here is that we have timeout only for unordered messages while there is n

Re: classnames.properties file is not updated and missed in 1.8 release

Well, the “classnames.properties” is not fully updated at build time. I’ve corrected the description of the ticket. https://issues.apache.org/jira/browse/IGNITE-2422 Maksim Kozlov, would you handle this? Anton V. and Vladimir O. can assist you

Re: IgniteConfiguration.gridName is very confusing

Support Pavel’s point of view. Also Alexander please make sure that your changes are merged into ignite-2.0 branch rather than to the master. I think this functionality has to be available in 2.0 first. Finally, please update 2.0 Migration Guide once you’ve finished with this task: https://cwi

2.0 Migration Guide

Igniters, There will be many changes in 2.0. Some API can be deprecated while the other removed completely. Let’s track all this kind of changes in 2.0 migration guide making a life for our users easier when they will be switching from 1.x to 2.0 version. Add this page to your bookmarks and don

Re: Extend TcpDiscoveryVmIpFinder functionality

If to do this as flexible as possible we can support ranges for every byte applying a format like the one below. 10.0.0.[1-10] [10-11].0.0.[1-10] 128.[165-165].10.[1-100] What do you think? — Denis > On Jan 10, 2017, at 3:08 AM, Sergey Kozlov wrote: > > I like the idea to use the full range

Re: Integration with RocketMQ

Roman, Makes perfect sense to me. Do you think we can release this feature in the nearest AI release (1.9 or 2.0) around February/March? — Denis > On Jan 10, 2017, at 7:57 PM, Roman Shtykh wrote: > > Denis, > I think our Kafka integration is the closest to what may be required for > RockerMQ

Re: Empty cache memory overhead

Alex G., Will this be still relevant in 2.0 when we’re expecting to release the page memory? https://issues.apache.org/jira/browse/IGNITE-3477 — Denis > On Jan 10, 2017, at 9:41 PM, Alexandr Kuramshin wrote: > > Hi community, > > I'd like

Re: Integration with RocketMQ

Denis, Yes, I plan to complete it by that time. #Btw, RocketMQ first release (4.0.0) under Apache license is planned for this month. Roman On Thursday, January 12, 2017 7:30 AM, Denis Magda wrote: Roman, Makes perfect sense to me. Do you think we can release this feature in the neare

Re: 2.0 Migration Guide

Denis, I would rather have these changes tracked on a hidden readme.io page. This way we can publish it whenever 2.0 is released. You can have the URL to that page on Ignite wiki. D. On Wed, Jan 11, 2017 at 2:18 PM, Denis Magda wrote: > Igniters, > > There will be many changes in 2.0. Some API

Re: DDL implementation details

Agree with Sergey. We should be able to specify cache properties inside of SQL statements. Does H2 have any support to process SQL hints? Can we change it? Having said that, while we finalize the above, I think we should start working on DDL implementation to use the default settings, as specified

Re: 2.0 Migration Guide

Dmitriy, Few number of people contribute to readme.io documentation and I don’t want to create an account only if someone needs to put a row in the migration guide. On the other hand, everyone can have an access to the wiki and update page there directly. I’ll create a page