Re: Extend TcpDiscoveryVmIpFinder functionality

Denis The initial idea was to have a simple ability to put ip address ranges. Probably we need to google how other products implement ip address ranges in its (Spring) configurations. On Thu, Jan 12, 2017 at 1:28 AM, Denis Magda wrote: > If to do this as flexible as possible we can support rang

Re: DDL implementation details

As first stage of DDL we can implement following CREATE TABLE statement support: - CREATE TABLE without cache properties (use default cache properties or cache properties defined in SQL Schema) - CREATE TABLE .. LIKE where we can create a cache based on an another existing cache. On Thu, Jan 12,

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

Well, I've seen the updated ticket. 2017-01-12 1:07 GMT+03:00 Denis Magda : > 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 < > https://issues.apache.org/jira/browse/IGNITE-

[GitHub] ignite pull request #1423: Ignite 4540

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

Re: Timeout for ordered message

Not sure what we are trying to achieve here. Unordered messages are simply ignored if there is no listener. We always expect unordered listeners to be installed before at least for internal messages, but this is not the case for some ordered messages, i.e. task session requests. --Yakov 2017-01-1

Re: Empty cache memory overhead

Yes, it is relevant. All of these structures are not replaced with page memory. On Thu, Jan 12, 2017 at 1:34 AM, Denis Magda wrote: > 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 > > — > Den

Re: Extend TcpDiscoveryVmIpFinder functionality

I would prefer simple range notation with ".." - 192.168.0.1..192.168.2.100 For all other cases user may implement their own IP finder or initialize IP finders we provide programmatically. --Yakov 2017-01-12 11:37 GMT+03:00 Sergey Kozlov : > Denis > > The initial idea was to have a simple abili

FOSDEM 2017 Open Source Conference - Brussels

Hello Everyone This email is to tell you about ASF participation at FOSDEM. The event will be held in Brussels on 4^th & 5^th February 2017 and we are hoping that many people from our ASF projects will be there. https://fosdem.org/2017/ Attending FOSDEM is completely free and the ASF will ag

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

Done. 2017-01-11 20:39 GMT+03:00 Dmitriy Setrakyan : > 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...@g

IGNITE-4302 discovery messages to exchange binary metadata - design proposal

Hello Ignite devs, I came up with the following design proposal for IGNITE-4302 , which is very similar to described here proposal for IGNITE-4157

Re: DDL implementation details

Alexander, Will we keep the old option to have multiple tables in one cache? If so, how will create table statement know which cache to choose? It seems to me that to be consistent with the current DML implementation we should have a CREATE SCHEMA statement which will define the cache and cache c

Re: DDL implementation details

I am afraid in this case user will have to define too much schemes - boilerplate. Does it make sense at all to pack multiple tuples into a single cache from user perspective? On Thu, Jan 12, 2017 at 4:40 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Alexander, > > Will we keep the o

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

I looked at the code. The PartitionSet concept looks overengineered to me, why wouldn't we just go with int[]? Sergi 2017-01-12 15:18 GMT+03:00 Alexei Scherbakov : > Done. > > 2017-01-11 20:39 GMT+03:00 Dmitriy Setrakyan : > > > Alexey, > > > > I am not sure I am seeing the API changes documente

Re: DDL implementation details

Hi, 1. For now I'm against inventing any custom SQL syntax and implementing parsing. Currently H2 supports the following syntax: CREATE TABLE test(...) WITH "myCustomParamString" This is enough for us to pass the needed parameters. 2. Agree with AG, we have to separate cache creation from table

Re: DDL implementation details

Sergi, Alexey G., I see your point and am rather inclined to agree that we should let current notion of "single schema - multiple tables" live. Still, if we create schema with cache config file, what's the whole point of SQL then if the user anyway has to write XML? This probably could be useful

Re: DDL implementation details

The xml config was only for example. We can put in this configuration string cache config parameters directly like this: CREATE SCHEMA "MyCacheName" WITH "cacheMode=REPLICATED;atomicityMode=ATOMIC" Sergi 2017-01-12 20:21 GMT+03:00 Alexander Paschenko < alexander.a.pasche...@gmail.com>: > Sergi,

Re: DDL implementation details

Sergi, OK, great. Still, what's up with CREATE TABLE? After a bit of code digging, I currently don't see major obstacles against registering query entities (i.e. type descriptors) on the fly - CREATE TABLE will essentially boil down to *GridQueryIndexing#registerType* call. But, as you have justl

Re: DDL implementation details

BTW, I have also did some H2 guts inspection, and, as I see it now, it's not impossible to do custom parsing without (an awful lot) of ugliness. What we would have to do is basically spoof private singleton org.h2.engine.Engine#INSTANCE on node start via reflection with our custom implementation th

[GitHub] ignite pull request #1424: Ignite 4540-1

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

Re: DDL implementation details

On Thu, Jan 12, 2017 at 10:16 AM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > Sergi, > > OK, great. Still, what's up with CREATE TABLE? After a bit of code > digging, I currently don't see major obstacles against registering > query entities (i.e. type descriptors) on the fly -

Re: DDL implementation details

On Thu, Jan 12, 2017 at 9:47 AM, Sergi Vladykin wrote: > The xml config was only for example. We can put in this configuration > string cache config parameters directly like this: > > CREATE SCHEMA "MyCacheName" WITH > "cacheMode=REPLICATED;atomicityMode=ATOMIC" > This approach makes sense, if i

Re: DDL implementation details

> On Jan 12, 2017, at 12:35 PM, Dmitriy Setrakyan wrote: > > On Thu, Jan 12, 2017 at 9:47 AM, Sergi Vladykin > wrote: > >> The xml config was only for example. We can put in this configuration >> string cache config parameters directly like this: >> >> CREATE SCHEMA "MyCacheName" WITH >> "cac

Re: DDL implementation details

Denis The affinity key term is close to the partition key definition for MySQL: https://dev.mysql.com/doc/refman/5.7/en/partitioning-key.html On Thu, Jan 12, 2017 at 11:46 PM, Denis Magda wrote: > > > On Jan 12, 2017, at 12:35 PM, Dmitriy Setrakyan > wrote: > > > > On Thu, Jan 12, 2017 at 9:47

Re: DDL implementation details

I am not quite sure I understand the idea of "SCHEMA == cache". Consider some small database with, say, ~30 tables. And user wants to migrate to Ignite. How is he supposed to do so? 30 schemas leading to rewrite of all his SQL scripts? Or 30 key-value pairs in a single cache leading to lack of flex

Re: DDL implementation details

Guys, As for the stages I would propose the following three creating separate JIRA tickets for them. Stage 1: - CREATE/DROP SCHEMA. - CREATE/DROP TABLE. Stage 2: - CREATE/DROP INDEX. - indexes are updated in the ‘lock-the-world mode' Stage 3: - CREATE/DROP INDEX. - indexes are updated concurre

Re: DDL implementation details

Alexander, not sure what is the point of creating a table without indexes. I would combine stage 1 and 2. On Thu, Jan 12, 2017 at 12:57 PM, Denis Magda wrote: > Guys, > > As for the stages I would propose the following three creating separate > JIRA tickets for them. > > Stage 1: > - CREATE/DROP

Re: Timeout for ordered message

Yakov, I'm talking only about user messages and public API. What is the purpose of the timeout in this case? I'm just trying to properly understand the semantics and at least fix the JavaDoc as it seems to be completely wrong now. -Val On Thu, Jan 12, 2017 at 2:41 AM, Yakov Zhdanov wrote: > N

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

On Thu, Jan 12, 2017 at 6:12 AM, Sergi Vladykin wrote: > I looked at the code. The PartitionSet concept looks overengineered to me, > why wouldn't we just go with int[]? > Agree. > > Sergi > > 2017-01-12 15:18 GMT+03:00 Alexei Scherbakov >: > > > Done. > > > > 2017-01-11 20:39 GMT+03:00 Dmitr

Configuring Cassandra persistence from code

Hi Igor, I just noticed that KeyValuePersistenceSettings class required to configure Cassandra store can be created only based on XML file of a special format. If so, this looks like a pretty serious limitation. First of all, when configuring such cache, user has to know both Spring configuration

SEO Audit of ignite.apache.org

I would like to help the Apache Ignite website attract more web traffic. To do that, I can launch an SEO audit of the website. The goals of the audit would be to: * - Make sure the site is easily crawled by search engines * - Find any duplicate content and recommend strategies

Re: SEO Audit of ignite.apache.org

Terry, The more traffic to Ignite website, the better. I think it will be great if you could do it. Thanks D. On Thu, Jan 12, 2017 at 3:41 PM, Terry Erisman wrote: > I would like to help the Apache Ignite website attract more web traffic. To > do that, I can launch an SEO audit of the website.

Re: Configuring Cassandra persistence from code

Good question. The main case for this getters/setters API is when you are going to dynamically create Cassandra persistence configuration for you cache. As I see it, in most cases developers will create kind of xml persistent descriptor template, which will be used to generate final persistence de

Re: DDL implementation details

Dima, >> But, as you have justly noted, we have to keep nodes joining the >> cluster up-to-date about what schemas and tables need to be created in >> order for those nodes to participate in distributed queries. And, >> correct me if I'm wrong, but this is relevant even outside of context >> of 2.

Re: DDL implementation details

Vova, 2017-01-13 4:56 GMT+08:00 Vladimir Ozerov : > I am not quite sure I understand the idea of "SCHEMA == cache". Consider > some small database with, say, ~30 tables. And user wants to migrate to > Ignite. How is he supposed to do so? 30 schemas leading to rewrite of all > his SQL scripts? Or 3