Re: Adding sqlline tool to Apache Ignite project

2017-10-06 Thread dsetrakyan
I like ignitesql. ⁣D.​ On Oct 6, 2017, 4:49 PM, at 4:49 PM, Vladimir Ozerov wrote: >Denis, > >Setting default host to 127.0.0.1 is bad idea, because it mean that in >practice users would have to change the script always. Instead, we >should >accept host name as argument. This is perfectly fine

Re: [DISCUSS] Ignite Update Checker

2017-09-30 Thread dsetrakyan
Why would we need googleads for youtube? Any chance to disable it? ⁣D.​ On Sep 30, 2017, 10:25 AM, at 10:25 AM, Prachi Garg wrote: >Yes, I see in dev tools that calls to googleads and doubleclick are >made >from Youtube. > >On Fri, Sep 29, 2017 at 4:33 PM, Denis Magda wrote: > >> I also did a g

Re: Logical Cache Documented

2017-09-30 Thread dsetrakyan
Why not? Obviously compression would have to be enabled per group, not per cache. ⁣D.​ On Sep 29, 2017, 10:50 PM, at 10:50 PM, Vladimir Ozerov wrote: >And it will continue hitting us in future. For example, when data >compression is implemented, for logical caches compression rate will be >poo

Re: Logical Cache Documented

2017-09-30 Thread dsetrakyan
Vova, cache groups almost never need to be touched by users. They should be configured automatically. To my knowledge,  by default all caches fall into the default group (please confirm). As far as scans, the performance should not be affected, as we now store  entries in B+trees and the data i

Re: Durable Memory and Ignite Persistence Tuning

2017-09-01 Thread dsetrakyan
Cos, great point! I think the Ignite community should start load testing with default settings, without any config changes. This should open a lot of holes. ⁣D.​ On Sep 1, 2017, 9:57 PM, at 9:57 PM, Konstantin Boudnik wrote: >Just to spice it up: in my experience, having a few hundred paramete

Re: How a new index is built in runtime?

2017-08-28 Thread dsetrakyan
Vova, how hard is it to make it multi-threaded? ⁣D.​ On Aug 28, 2017, 10:05 AM, at 10:05 AM, Vladimir Ozerov wrote: >Denis, > >We iterate over the whole cache and build the index entry-by-entry. >Control >is returned back to the user when index is ready. > >On Fri, Aug 18, 2017 at 9:50 AM, Yak

Re: [IGNITE-5717] improvements of MemoryPolicy default size

2017-08-04 Thread dsetrakyan
But why? We allocate the memory, so we should know when it runs out. What am i missing? ⁣D.​ On Aug 4, 2017, 11:55 AM, at 11:55 AM, Sergey Chugunov wrote: >I used GC and java only as an example, they are not applicable to >Ignite >case where we manage offheap memory. > >My point is that there

Re: [IGNITE-5717] improvements of MemoryPolicy default size

2017-08-04 Thread dsetrakyan
Hang on. I thought we were talking about offheap size, GC should not be relevant. Am I wrong? ⁣D.​ On Aug 4, 2017, 11:38 AM, at 11:38 AM, Sergey Chugunov wrote: >Do you see an obvious way of implementing it? > >In java there is a heap and GC working on it. And for instance, it is >possible to

Re: [IGNITE-5717] improvements of MemoryPolicy default size

2017-08-04 Thread dsetrakyan
Without #3, the #1 and #2 make little sense. Why is #3 so difficult? ⁣D.​ On Aug 4, 2017, 10:46 AM, at 10:46 AM, Sergey Chugunov wrote: >Dmitriy, > >Last item makes perfect sense to me, one may think of it as an >"OutOfMemoryException" in java. >However, it looks like such feature requires con

Re: Cluster auto activation design proposal

2017-08-03 Thread dsetrakyan
Yakov, I think it is not just restarts, this set of nodes is minimally required for the cluster to function, no? ⁣D.​ On Aug 3, 2017, 11:23 AM, at 11:23 AM, Yakov Zhdanov wrote: >Ю> How about naming it "minimal node set" or "required node set"? > >Required for what? I would add restart if the

Re: Cluster auto activation design proposal

2017-08-03 Thread dsetrakyan
How about naming it "minimal node set" or "required node set"? ⁣D.​ On Aug 3, 2017, 11:15 AM, at 11:15 AM, Yakov Zhdanov wrote: >> * Based on some sort of policies when the actual cluster topology >differs >too much from the baseline or when some critical condition happens >(e.g., >when there a

Re: Thin client protocol message format

2017-08-03 Thread dsetrakyan
Got it, thanks! On Aug 3, 2017, 11:04 AM, at 11:04 AM, Vladimir Ozerov wrote: >Dima, > >Our goal is to have a format, which will work for both synchronous, >asynchronous, single-threaded and multi-threaded clients. All we need >to >achieve this is "request ID" propagated from request to response

Re: [IGNITE-5717] improvements of MemoryPolicy default size

2017-08-01 Thread dsetrakyan
Vova, 1GB seems a bit too small for me, and frankly i do not want t o guess. Why not allocate in increments automatically? ⁣D.​ On Aug 1, 2017, 11:03 PM, at 11:03 PM, Vladimir Ozerov wrote: >Denis, >No doubts you haven't heard about it - AI 2.1 with persistence, when >80% of >RAM is allocated

Re: Data compression in Ignite 2.0

2017-08-01 Thread dsetrakyan
I would prefer that we reuse an existing compression protocol, but at the table level. If not possible, then we should go with a shared mapping approach. Any idea how hard? ⁣D.​ On Aug 1, 2017, 11:15 AM, at 11:15 AM, Vladimir Ozerov wrote: >Vyacheslav, > >This is not about my needs, but abou

Re: Create own SQL parser

2017-08-01 Thread dsetrakyan
Vova, I am not sure what you are proposing... extending H2 parser with new syntax or a brand new parser? ⁣D.​ On Aug 1, 2017, 4:26 PM, at 4:26 PM, Vladimir Ozerov wrote: >Andrey, > >Note that I am not proposing to remove H2 as a whole. Main point for >now is >to support missing pieces of DDL s

Re: [IGNITE-5717] improvements of MemoryPolicy default size

2017-08-01 Thread dsetrakyan
I prefer option #1. ⁣D.​ On Aug 1, 2017, 11:20 AM, at 11:20 AM, Sergey Chugunov wrote: >Folks, > >I would like to get back to the question about MemoryPolicy maxMemory >defaults. > >Although MemoryPolicy may be configured with initial and maxMemory >settings, when persistence is used MemoryPoli

Re: Thin client protocol message format

2017-08-01 Thread dsetrakyan
Backward compatible? ⁣D.​ On Aug 1, 2017, 7:04 PM, at 7:04 PM, Pavel Tupitsyn wrote: >Dmitry, we don't need any reserved bytes, because protocol is >versioned. > >On Tue, Aug 1, 2017 at 7:49 PM, wrote: > >> We should also leave 8 bytes of empty space for future changes. >> >> ⁣D.​ >> >> On Aug

Re: Thin client protocol message format

2017-08-01 Thread dsetrakyan
We should also leave 8 bytes of empty space for future changes. ⁣D.​ On Aug 1, 2017, 6:41 PM, at 6:41 PM, Pavel Tupitsyn wrote: >Alexey, good idea. ODBC and JDBC could also benefit from this. > >On Tue, Aug 1, 2017 at 7:27 PM, Alexey Kuznetsov > >wrote: > >> Pavel, >> >> How about data compress

Re: Resurrect FairAffinityFunction

2017-07-24 Thread dsetrakyan
Agree with Val, we should bring it back. ⁣D.​ On Jul 24, 2017, 8:14 PM, at 8:14 PM, Valentin Kulichenko wrote: >Guys, > >Some time ago we removed FairAffinityFunction from the project. >However, my >communication with users clearly shows that is was a rush decision. >Distribution showed by Fair

Re: Ignite ML status update

2017-07-20 Thread dsetrakyan
Sounds good. On Jul 20, 2017, 1:56 PM, at 1:56 PM, Yury Babak wrote: >Dmitriy, I can do it. But as far as I know Oleg Ignatenko already wrote >blog >about Ignite ML. But it only about AI 2.0 and only on >Russian(Habrahabr). So >we could translate this post in English. > >And also I can write a bl

Re: New method for MemoryMetrics: segment fill variance

2017-07-19 Thread dsetrakyan
Sounds good! ⁣D.​ On Jul 19, 2017, 1:54 PM, at 1:54 PM, Ivan Rakov wrote: >Dmitriy, > >I agree, hashFunctionScore is more comprehensible. >I'd correct it to "pageHashFunctionScore" to make it clear that it's >about function that distributes pages, not about hashCode() of >user-provided keys. > >

Re: usage analytics

2017-07-18 Thread dsetrakyan
I would try to ping legal again and see if they respond. If not, I think we will need to come up with a simpler approach, that does not require legal approval. ⁣D.​ On Jul 18, 2017, 2:23 PM, at 2:23 PM, Nikita Ivanov wrote: >Igniters, >Just a quick update. I haven't gotten response from ASF Le

Re: Replace Cron4J with Quartz for ignite-schedule module.

2017-06-21 Thread dsetrakyan
Probably a good task for a newbie. ⁣D.​ On Jun 21, 2017, 9:41 AM, at 9:41 AM, Alexey Kuznetsov wrote: >Done, > >https://issues.apache.org/jira/browse/IGNITE-5565 > >I think it could take a couple of days in background mode. > >On Wed, Jun 21, 2017 at 1:40 PM, Dmitriy Setrakyan > >wrote: > >> Th

Re: IGFS concurrency issue

2015-09-30 Thread dsetrakyan
Vladimir Ozerov wrote > This is how we fixed it for now. But it requires paths locking starting > from the root. Otherwise they can become parent-child in a moment after > sucessfull check. I am not sure if we should be concerned about looking at the root or path here. This lock is only held for t