Re: The Spark 2.4 support

2019-09-30 Thread Ivan Pavlukhin
, 30/09/2019 в 20:29 +0300, Alexey Zinoviev пишет: > > > > > Yes, as I understand it uses Spark internals from the first commit))) > > > > > The reason - we take Spark SQL query execution plan and try to > > execute it > > > > &g

Re: Unassigned issue IGNITE-12174

2019-10-01 Thread Ivan Pavlukhin
would be even better to handle this unsupported use case in the > code as well instead of throwing a NullPointerException. I can add > this check as improvement to the Ignite code if this is wanted and > agreed. But I need a hint on what would be the right place to add this > check i

Re: [DISCUSSION][IEP-35] Replace RunningQueryManager with GridSystemViewManager

2019-10-02 Thread Ivan Pavlukhin
> SystemView API. > > Any objections? > > [1] https://issues.apache.org/jira/browse/IGNITE-10754 > [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392 > [3] https://issues.apache.org/jira/browse/IGNITE-12223 > [4] https://issues.apache.org/jira/browse/IGNITE-12224 -- Best regards, Ivan Pavlukhin

Re: The Spark 2.4 support

2019-09-30 Thread Ivan Pavlukhin
7 from 211 tests are muted now) > > Please, if somebody interested in it, make an initial review of modular > ignite structure and changes (without deep diving into Spark code). > > And yes, the proposed code is a copy-paste of spark-ignite module with a > few fixes -- Best regards, Ivan Pavlukhin

Re: nodes are restarting when i try to drop a table created with persistence enabled

2019-09-30 Thread Ivan Pavlukhin
Hi, Stacktrace and exception message has some valuable details: org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to find a page for eviction [segmentCapacity=126515, loaded=49628, maxDirtyPages=37221, dirtyPages=49627, cpPages=0, pinnedInSegment=1, failedToPrepare=49628] I see a

Re: New SQL execution engine

2019-09-30 Thread Ivan Pavlukhin
w. > > > > > > Some of them are critical (like impossibility to execute particular > > > queries), some of them are majors (like impossibility to execute > > > particular > > > queries without pre-preparation your data to have a collocation) and many > > > minors. > > > > > > Most of the issues cannot be solved without whole engine redesign. > > > > > > So, here the proposal: > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=130028084 > > > > > > I'll appreciate if you share your thoughts on top of that. > > > > > > Regards, > > > Igor > > > -- Best regards, Ivan Pavlukhin

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-09-30 Thread Ivan Pavlukhin
t; > > > >> > > > components. > > > > >> > > > > > > > > > > > > > > > >> > > > > > > > > > > > On Fri, 20 Sep 2019 at 17:24, Alexey > > Zinoviev < > > > > >> > > > > > > > >> > > > zaleslaw@gmail.com> > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > wrote: > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > I wrote about code freeze at December 18, > > > > 2019, ok, > > > > >> > we > > > > >> > > > > > > > >> > > > can move one > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > week > > > > >> > > > > > > > > > > > > earlier to 11 December > > > > >> > > > > > > > > > > > > Voting + Release could be after 10th > > January. > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > пт, 20 сент. 2019 г. в 15:43, Maxim > > Muzafarov < > > > > >> > > > > > > > >> > > > mmu...@apache.org>: > > > > >> > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Alexey, > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > It is not a problem to shift release a > > bit > > > > later or > > > > >> > > > > > > > >> > > > earlier, but I'm > > > > >> > > > > > > > > > > > > > strictly against having `code freeze` > > stage > > > > on > > > > >> > > > > > > > >> > > > holidays (the > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > Christmas > > > > >> > > > > > > > > > > > > > holidays at the end of December and New > > Year > > > > >> > holidays > > > > >> > > > > > > > >> > > > at the > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > beginning > > > > >> > > > > > > > > > > > > > of January). From my point, it's better > > to > > > > have it > > > > >> > > > > > > > >> > > > completed `code > > > > >> > > > > > > > > > > > > > freeze` stage before December 23th or > > > > started after > > > > >> > > > > > > > >> > > > 10th January. > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > Thoughts? > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > On Fri, 20 Sep 2019 at 15:09, Dmitriy > > Pavlov > > > > < > > > > >> > > > > > > > >> > > > dpav...@apache.org> > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > wrote: > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > +1 For Maxim as release manager. > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > Maxim, > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > It is a good thing that you have > > committer > > > > >> > rights, > > > > >> > > > > > > > >> > > > and most of > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > the steps > > > > >> > > > > > > > > > > > > > > you will be able to complete yourself. > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > But please engage one from PMC member > > to > > > > complete > > > > >> > > > > > > > >> > > > steps from the > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > release > > > > >> > > > > > > > > > > > > > > process where PMC rights are required > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > >> > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process At > > > > >> > > > > > > > > > > > > > > least, access to docker and nuget creds > > > > requires > > > > >> > PMC > > > > >> > > > > > > > >> > > > membership. > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > Feel free to ping me, I will assist, as > > > > well. > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > Sincerely, > > > > >> > > > > > > > > > > > > > > Dmitriy Pavlov > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > пт, 20 сент. 2019 г. в 14:59, Alexey > > > > Zinoviev < > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > zaleslaw@gmail.com>: > > > > >> > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > For Spark and ML components the best > > > > dates > > > > >> > should > > > > >> > > > > > > > >> > > > be moved to > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > one month > > > > >> > > > > > > > > > > > > > > > later, what's about? > > > > >> > > > > > > > > > > > > > > > There are a lot of features there, > > but a > > > > lot of > > > > >> > > > > > > > >> > > > bugs and minor > > > > >> > > > > > > > > > > > > > > > improvements in JIRA too > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > Also I support you as a release > > manager > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > Scope Freeze: December 4, 2019 > > > > >> > > > > > > > > > > > > > > > Code Freeze: December 18, 2019 > > > > >> > > > > > > > > > > > > > > > Voting Date: January 10, 2019 > > > > >> > > > > > > > > > > > > > > > Release Date: January 17, 2019 > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > пт, 20 сент. 2019 г. в 14:44, Maxim > > > > Muzafarov < > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > mmu...@apache.org>: > > > > >> > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > Igniters, > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > It's almost a year has passed since > > > > the last > > > > >> > > > > > > > >> > > > major Apache > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > Ignite 2.7 > > > > >> > > > > > > > > > > > > > > > > has been released. We've > > accumulated a > > > > lot of > > > > >> > > > > > > > >> > > > performance > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > improvements > > > > >> > > > > > > > > > > > > > > > > and a lot of new features which are > > > > waiting > > > > >> > for > > > > >> > > > > > > > >> > > > their release > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > date. > > > > >> > > > > > > > > > > > > > > > > Here is my list of the most > > interesting > > > > >> > things > > > > >> > > > > > > > >> > > > from my point > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > since > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > the > > > > >> > > > > > > > > > > > > > > > > last major release: > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > Service Grid, > > > > >> > > > > > > > > > > > > > > > > Monitoring, > > > > >> > > > > > > > > > > > > > > > > Recovery Read > > > > >> > > > > > > > > > > > > > > > > BLT auto-adjust, > > > > >> > > > > > > > > > > > > > > > > PDS compression, > > > > >> > > > > > > > > > > > > > > > > WAL page compression, > > > > >> > > > > > > > > > > > > > > > > Thin client: best effort affinity, > > > > >> > > > > > > > > > > > > > > > > Thin client: transactions support > > (not > > > > yet) > > > > >> > > > > > > > > > > > > > > > > SQL query history > > > > >> > > > > > > > > > > > > > > > > SQL statistics > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > I think we should no longer wait > > and > > > > freeze > > > > >> > the > > > > >> > > > > > > > >> > > > master branch > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > anymore > > > > >> > > > > > > > > > > > > > > > > and prepare the next major release > > by > > > > the > > > > >> > end of > > > > >> > > > > > > > >> > > > the year. > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > I propose to discuss Time, Scope of > > > > Apache > > > > >> > > > > > > > >> > > > Ignite 2.8 release > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > and > > > > >> > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > also > > > > >> > > > > > > > > > > > > > > > > I want to propose myself to be the > > > > release > > > > >> > > > > > > > >> > > > manager of the > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > planning > > > > >> > > > > > > > > > > > > > > > > release. > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > Scope Freeze: November 4, 2019 > > > > >> > > > > > > > > > > > > > > > > Code Freeze: November 18, 2019 > > > > >> > > > > > > > > > > > > > > > > Voting Date: December 10, 2019 > > > > >> > > > > > > > > > > > > > > > > Release Date: December 17, 2019 > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > > > WDYT? > > > > >> > > > > > > > > > > > > > > > > > > > > >> > > > > > >> > > > > >> -- > > > > >> BR, Sergey Antonov > > > > > > -- Best regards, Ivan Pavlukhin

Re: [DISCUSSION][IEP-35] Replace RunningQueryManager with GridSystemViewManager

2019-10-04 Thread Ivan Pavlukhin
ll clear now? > > [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392 > > В Ср, 02/10/2019 в 17:21 +0300, Ivan Pavlukhin пишет: > > Hi Nikolay, > > > > Actually I do not fully understand what is SystemView API. I have not > &g

Re: Calcite based SQL query engine. Local queries

2019-11-07 Thread Ivan Pavlukhin
e > manually that a distributed phase is redundant via 'local' flag or by other > means. > > Does it make things clearer? > > > - > Denis > > > On Thu, Nov 7, 2019 at 3:53 AM Ivan Pavlukhin wrote: > > > Stephen, > > > > In my understanding we need

Re: Calcite based SQL query engine. Local queries

2019-11-07 Thread Ivan Pavlukhin
of data across > >> the grid. You’d broadcast a closure, running the same code on every node > >> with just the local data. SQL doesn’t work in isolation — it’s often used > >> as a filter for future computations. > >> > >> Regards, > >> Stephen > >&

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-10-30 Thread Ivan Pavlukhin
is > > > > >>>>>>> release? > > > > >>>>>>> > > > > >>>>>>> - > > > > >>>>>>> Denis > > > > >>>>>>> > > > > >&

Re: [DISCUSS] Proposal for Ignite Extensions as a separate Bahir module or Incubator project

2019-11-01 Thread Ivan Pavlukhin
; > >> > > > > > >> After thinking about it for the last few days, I think that the > > best > > > > > >> approach to start with should be as follows: > > > > > >> > > > > > >>1. Let's create an "ignite-extensions&qu

Re: Calcite based SQL query engine. Local queries

2019-11-12 Thread Ivan Pavlukhin
ith > key-value and scans but with SQL as well that supports conditions, joins, > etc. > > Denis > > On Thursday, November 7, 2019, Ivan Pavlukhin wrote: > > > Denis, > > > > To make things really clearer we need to provide some concrete example > > of

Re: Please Authrorize GG's instance of AI TC bot to run backround checks

2019-11-18 Thread Ivan Pavlukhin
rize Server' menu item near the user > name? This will enable the bot to run all background checks. > > Technically anyone can authorize the server, but it is better that > GridGainer will do it. > > Sincerely, > Dmitriy Pavlov -- Best regards, Ivan Pavlukhin

Re: Collocated/replicatedOnly flags for Thin JDBC driver

2019-11-18 Thread Ivan Pavlukhin
g. > > > > I guess both flags should be deprecated and removed (2.8?). > > > > Ideally *distrubitedJoins *should be removed as well and replaced by query > > hints (default *distrubitedJoins=true*) > > > > 1. https://apacheignite-sql.readme.io/docs/jdbc-driver > > 2. https://issues.apache.org/jira/browse/IGNITE-6296 > > 3. https://issues.apache.org/jira/browse/IGNITE-12372 > > -- > > Sergey Kozlov > > GridGain Systems > > www.gridgain.com > > -- Best regards, Ivan Pavlukhin

Re: New SQL execution engine

2019-11-18 Thread Ivan Pavlukhin
uld > record it as such. As the behavior is different with and without the > parallelism and there is no warning during execution or in the api. > > Any thought? > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ -- Best regards, Ivan Pavlukhin

Re: Please Authrorize GG's instance of AI TC bot to run backround checks

2019-11-18 Thread Ivan Pavlukhin
horized so my request is not relevant. > > Now it should be up and running as usual. If not, please reply here or on > some another topic in the list. > > Sincerely > Dmitriy Pavlov > > пн, 18 нояб. 2019 г. в 11:19, Ivan Pavlukhin : > > > Dmitriy, > > >

Re: Please Authrorize GG's instance of AI TC bot to run backround checks

2019-11-18 Thread Ivan Pavlukhin
ggering for new builds is started. > > TC Bot doesn't have standalone credentials for TC server(s) configured. > Only host(s) is specified in the conf/properties. > > > пн, 18 нояб. 2019 г. в 15:08, Ivan Pavlukhin : > > > Dmitriy, > > > > Could you please clari

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-11-05 Thread Ivan Pavlukhin
Maxim, Could you please elaborate about a question from Akash. What tickets do we consider for release? All with 2.8 fix version in Jira or there is a different criteria? вт, 5 нояб. 2019 г. в 15:01, Ivan Pavlukhin : > > Alexey, > > True. It is definitely to early for Calcite. &g

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-11-05 Thread Ivan Pavlukhin
Folks, What about IGFS and Hadoop Accelerator discontinuation [1]? [1] https://issues.apache.org/jira/browse/IGNITE-11942 вт, 5 нояб. 2019 г. в 15:03, Ivan Pavlukhin : > > Maxim, > > Could you please elaborate about a question from Akash. What tickets > do we consider for releas

Re: [RESULT] Ignite PMC Chair Vote

2019-11-06 Thread Ivan Pavlukhin
ave two candidates who got equal votes - Alexey and > > Nikolay. Please give Ignite PMC some time to figure out how to proceed > > further. > > > > > > - > > Denis > > -- Best regards, Ivan Pavlukhin

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-11-05 Thread Ivan Pavlukhin
Apache+Ignite+2.8#ApacheIgnite2.8-Releaseissuesgroupedbystatus > > > > > > Just wanted to make sure its a part on 2.8. > > > > > > Thanks, > > > Akash > > > > > > On Wed, Oct 30, 2019 at 8:20 PM Ivan Pavlukhin > > wrote: &g

Re: Calcite based SQL query engine. Local queries

2019-11-08 Thread Ivan Pavlukhin
t Map-Reduce. > > It may be there is another way of doing that, so I encourage to share it. I > could update workshops/training I preparing in background. > > Sincerely, > Dmitriy Pavlov > > пт, 8 нояб. 2019 г. в 08:57, Ivan Pavlukhin : > > > Denis, > > >

Re: Full-text queries in Thin Client protocol

2019-12-04 Thread Ivan Pavlukhin
remember in-person discussions with some community > > > members along the lines of > > > "Ignite full-text search capabilities may be deprecated or reworked soon, > > > let's not add to thin clients". > > > > > > Any insights on this? Thoughts, objections? > > > > > > Thanks, > > > Pavel > > > > > > > > > > > > > > -- Best regards, Ivan Pavlukhin

Re: [DISCUSS] Links to commercial version resources in community wiki

2019-12-04 Thread Ivan Pavlukhin
to refer > > > to it. Based on Alexey's response in another thread, that GridGain page > > > brings more clarity to the topic, thus, don't see any issue with that. > > > > > > > > > - > > > Denis > > > > > > > > > On Tue, Dec 3, 2019 a

Re: Joining node validation failure event.

2019-12-03 Thread Ivan Pavlukhin
led > joining attempt. Am I missing something? > > Regards, > Mikhail. > > On 03.12.2019 8:48, Ivan Pavlukhin wrote: > > Mikhail, > > > > Do you need some ordering guarantees among node lifecycle events and > > listener notifications. For example, I can imagi

Re: Joining node validation failure event.

2019-12-03 Thread Ivan Pavlukhin
y join failed. > > > 3 дек. 2019 г., в 12:22, Ivan Pavlukhin написал(а): > > > > Mikhail, > > > > So, I suppose there should be ordering guarantees that listener is > > registered before first validation failure can occur. Hope > > GridComponent#onK

Re: Joining node validation failure event.

2019-12-03 Thread Ivan Pavlukhin
Exception(s) from component(s) that don’t want node joined. > > > >> 3 дек. 2019 г., в 12:39, Ivan Pavlukhin написал(а): > >> > >> How that reason will look like? Actually, I mostly thinking about > >> general API here. What I would like to avoid is e

Re: Joining node validation failure event.

2019-12-02 Thread Ivan Pavlukhin
on. Maybe it can be solved some other way? I will appreciate > >> any suggestion or review PR [1] with event implementation. > >> > >> > >> [1] https://github.com/apache/ignite/pull/7057 > >> > >> > >> Regards, > >> > >> Mik

[DISCUSS] Links to commercial version resources in community wiki

2019-12-03 Thread Ivan Pavlukhin
be there is some common practice in ASF communities about the subject. Please, share your thoughts. [1] https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency -- Best regards, Ivan Pavlukhin

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-12-03 Thread Ivan Pavlukhin
*on topologies вт, 3 дек. 2019 г. в 17:15, Ivan Pavlukhin : > > Ilya, Yuriy, > > It seems that text queries can return incorrect results on tologies > with MOVING partitions. I left a comment in JIRA [1]. > > [1] https://issues.apache.org/jira/browse/IGNITE-12401 > >

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-12-03 Thread Ivan Pavlukhin
Ilya, Yuriy, It seems that text queries can return incorrect results on tologies with MOVING partitions. I left a comment in JIRA [1]. [1] https://issues.apache.org/jira/browse/IGNITE-12401 пн, 2 дек. 2019 г. в 15:00, Ivan Pavlukhin : > > Ilya, > > I checked your test on a rev

Re: Joining node validation failure event.

2019-12-04 Thread Ivan Pavlukhin
Mikhail, Yes I am fine with the approach. ср, 4 дек. 2019 г. в 20:30, Mikhail Petrov : > > Ivan, > > Am I right, that current approach to solving this problem looks good for > you? > > Regards, > Mikhail. > > On 03.12.2019 15:12, Ivan Pavlukhin wrote: &

Re: [DISCUSS] dependencies and release process for Ignite Extensions

2019-12-09 Thread Ivan Pavlukhin
chive for a download > >>with the name like "ignite-core-2.9+" > >> > >> > >> - > >> Denis > >> > >> > >> On Tue, Nov 26, 2019 at 9:03 PM Saikat Maitra > >> wrote: > >> > >> > Hello, > >> > > >> > I wanted to connect and discuss on the release process for > >> > ignite-extensions. As of today all our integrations since released > >> together > >> > were able to run build based on latest snapshot for example the current > >> > build depends on 2.8.0-SNAPSHOT. If we are making ignite-extensions as > >> > separate project with different release cycle then it make sense to have > >> > dependencies on core modules based on released artifact for example the > >> > dependency for ignite-core would be 2.7.6 > >> > > >> > Please review and share your thoughts. > >> > > >> > PR https://github.com/apache/ignite-extensions/pull/1 > >> > > >> > Regards > >> > Saikat > >> > > >> > > -- Best regards, Ivan Pavlukhin

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-12-09 Thread Ivan Pavlukhin
; > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Awatingfeaturescompletion > > > > > > > > > > > > > > On Thu, 7 Nov 2019 at 18:01, Maxim Muzafarov > > > > wrote: > > > > >

Re: Joining node validation failure event.

2019-12-09 Thread Ivan Pavlukhin
7057 > > Regards, > Mikhail. > > On 04.12.2019 21:54, Ivan Pavlukhin wrote: > > Mikhail, > > > > Yes I am fine with the approach. > > > > ср, 4 дек. 2019 г. в 20:30, Mikhail Petrov : > >> Ivan, > >> > >> Am I right, tha

Re: Data consistency essentials explained

2019-12-09 Thread Ivan Pavlukhin
GG docs have more clear information on the subject. > As soon as community will improve docs quality link could be changed back > to Apache. > > сб, 30 нояб. 2019 г. в 17:22, Ivan Pavlukhin : > > > Alexei, > > > > > Ivan, the link is intentional. > >

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

2019-12-09 Thread Ivan Pavlukhin
r in the master branch. I suppose > there will be enough of such changes to perform a next minor release > (e.g. 2.8.1) with such fixes. > > P.S. The issue [1] doesn't seem to be a truly release `blocker`. > > [1] https://issues.apache.org/jira/browse/IGNITE-12424 > > On Mon, 9

Re: [TeamCIty] Issues with the disc space

2019-12-09 Thread Ivan Pavlukhin
t; > aitc-lin05_01 > > aitc-lin04_04 > > > > On Fri, Dec 6, 2019 at 2:22 PM Ivan Pavlukhin wrote: > > > >> aitc-lin08 was handled as well. > >> > >> пт, 6 дек. 2019 г. в 10:41, Maxim Muzafarov : > >> > > >> > Ivan, > >>

Re: Data consistency essentials explained

2019-12-09 Thread Ivan Pavlukhin
Thank you! пн, 9 дек. 2019 г. в 19:08, Alexei Scherbakov : > > Ivan, > > It's true. The article is relevant for upcoming 2.8 release. I've added a > remark on that. > > пн, 9 дек. 2019 г. в 15:44, Ivan Pavlukhin : > > > Alexei, > > > > Am I get

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-12-13 Thread Ivan Pavlukhin
ring querying? > > BR, > Yuriy Shluiha > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ -- Best regards, Ivan Pavlukhin

Re: [ANNOUNCE] New Apache Ignite PMC member: Ivan Pavlukhin

2019-12-13 Thread Ivan Pavlukhin
, > > > > > > > > > > > > The Project Management Committee (PMC) for Apache Ignite has invited Ivan > > > Pavlukhin to become a PMC member and we are pleased to announce that he > > has > > > accepted. > > > > > > > >

Re: Adding support for Ignite secondary indexes to Apache Calcite planner

2019-12-11 Thread Ivan Pavlukhin
t;> method. > > >>> 3. Right before the query execution Calcite selects all materialized > > >>> views (indexes) which can be potentially used in query. > > >>> 4. During the query optimization indexes are registered by planner as > > >>> usual TableScans and hence can be chosen by optimizer if they have > > lower > > >>> cost. > > >>> > > >>> This sketch shows the ability to exploit index sortedness only. So the > > >>> future work in this direction should be focused on using indexes for > > >>> fast index lookups. At first glance FilterableTable and > > >>> FilterTableScanRule are good points to start. We can push Filter into > > >>> the TableScan and then use FilterableTable for fast index lookups > > >>> avoiding reading the whole index on TableScan step and then filtering > > >>> its output on the Filter step. > > >>> > > >>> What do you think? > > >>> > > >>> > > >>> > > >>> [1] > > >>> > > >> > > http://apache-ignite-developers.2346864.n4.nabble.com/New-SQL-execution-engine-tt43724.html#none > > >>> [2] > > >>> > > >> > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine > > >>> [3] https://issues.apache.org/jira/browse/PHOENIX-2047 > > >>> [4] https://issues.apache.org/jira/browse/DRILL-6381 > > >>> [5] https://issues.apache.org/jira/browse/DRILL-3929 > > >>> [6] https://github.com/apache/ignite/pull/7115 > > >> > > >> > > >> > > >> > > > > > -- Best regards, Ivan Pavlukhin

Re: [MTCGA]: new failures in builds [4815611] needs to be handled

2019-12-05 Thread Ivan Pavlukhin
=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheLoaderWriterTest.shouldLoadMultipleNonExistingEntryUsingLoadAll > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-931332770095255753=%3Cdefault%3E=testDetails > > *Recently contributed test failed in master > org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughUsingInvoke_setValue_CreateEntryThenRemove > > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7011147375211443911=%3Cdefault%3E=testDetails > Changes may lead to failure were done by > - nsamelchev > https://ci.ignite.apache.org/viewModification.html?modId=893531 > - sk0x50 > https://ci.ignite.apache.org/viewModification.html?modId=893515 > - nsamelchev > https://ci.ignite.apache.org/viewModification.html?modId=893523 > > - Here's a reminder of what contributors were agreed to do > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > - Should you have any questions please contact dev@ignite.apache.org > > Best Regards, > Apache Ignite TeamCity Bot > https://github.com/apache/ignite-teamcity-bot > Notification generated at 06:35:46 06-12-2019 -- Best regards, Ivan Pavlukhin

Re: BinaryObject API confuses users

2019-12-06 Thread Ivan Pavlukhin
der("testVal") > .setField("name", "John Doe", String.class); > > builder.setField("name", builder.getField("name")); > } > } > } > ``` > > [1] https://docs.oracle.com/javase/specs/jls/se11/html/jls-15.html#jls-15.12.2 -- Best regards, Ivan Pavlukhin

Re: [TeamCIty] Issues with the disc space

2019-12-06 Thread Ivan Pavlukhin
t; Failed to download file 'ignite.zip': No space left on device > > > > [1] > > https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=4814624 > > > > On Thu, 5 Dec 2019 at 15:13, Ivan Pavlukhin wrote: > > > > > > Folks, > >

Re: [TeamCIty] Issues with the disc space

2019-12-05 Thread Ivan Pavlukhin
isc space [1] > > > Can someone take a look? > > > > > > [1] > > https://ci.ignite.apache.org/viewLog.html?buildId=4809938=buildResultsDiv=IgniteTests24Java8_PlatformCPPLinuxClang > > -- Best regards, Ivan Pavlukhin

Re: Hello Ignite Community!

2019-12-05 Thread Ivan Pavlukhin
e and want to start with this issue - IGNITE-12303, my JIRA > > username hadoop1024. Any help on this will be appreciated. > > > > Btw,I have used ignite for real online systems and I find it really good. > > So, I want to learn more about it by contributing code. > > > > Thanks! > > > > Wang Cheng > > -- Best regards, Ivan Pavlukhin

Re: Cache 6 suite is broken

2019-12-16 Thread Ivan Pavlukhin
An update. After increasing NetworkTimeout [1] the test passes rarely [2]. [1] https://github.com/apache/ignite/pull/7142/files [2] https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=pull%2F7142%2Fhead=overview пн, 16 дек. 2019 г. в 09:07, Ivan Pavlukhin : > &

Cache 6 suite is broken

2019-12-15 Thread Ivan Pavlukhin
=%3Cdefault%3E=overview [2] https://github.com/apache/ignite/pull/7142/files -- Best regards, Ivan Pavlukhin

Re: [ANNOUNCE] New committer: Aleksei Scherbakov

2019-12-16 Thread Ivan Pavlukhin
> internals. > > > > Being a committer enables easier contribution to the project since there > > is > > no need to go via the patch submission process. This should enable better > > productivity. > > > > Aleksei, thank you! > > > > Best Regards, > > Dmitriy Pavlov > > on behalf of Apache Ignite PMC -- Best regards, Ivan Pavlukhin

Re: When Cache Metrics are switched on (statisticsEnabled = true) the empty cache events arrive to the client nodes

2019-12-16 Thread Ivan Pavlukhin
; > > > > > > > > > > > > > чт, 12 дек. 2019 г. в 17:20, > > roman.koria...@t-systems.com<mailto:roman.koria...@t-systems.com>>>: > > > > > > > > > > > > > Hi everyone, > > > > > > > I'd like to participate in this project! > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > T-Systems RUS > > > > > > > Point of Production > > > > > > > Roman Koriakov > > > > > > > Software Developer > > > > > > > Kirova 11, Voronezh, Russia > > > > > > > Tel: + 7 473 200 15 30 > > > > > > > E-mail: > > > roman.koria...@t-systems.com<mailto:roman.koria...@t-systems.com<mailto:roman.koria...@t-systems.com%3cmailto:roman.koria...@t-systems.com> > > > <mailto:roman.koria...@t-systems.com%3cmailto:roman.koria...@t-systems.com > > > >> > > > > > > > http://www.t-systems.com<http://www.t-systems.ru/<<http://www.t-systems.com%3chttp:/www.t-systems.ru/%3c> > > > http://www.t-systems.com%3chttp:/www.t-systems.ru/>> > > > > > > > > > > > > > > > > > -- Best regards, Ivan Pavlukhin

Re: When Cache Metrics are switched on (statisticsEnabled = true) the empty cache events arrive to the client nodes

2019-12-16 Thread Ivan Pavlukhin
; > > > > > > > > > > > > > > > > I will need an Apache JIRA username to add you to contributors. Can you > > > > > provide it? > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > -- > > > > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > чт, 12 дек. 2019 г. в 17:20, > > > > roman.koria...@t-systems.com<mailto:roman.koria...@t-systems.com>>>: > > > > > > > > > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > I'd like to participate in this project! > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > > > T-Systems RUS > > > > > > > > > > > Point of Production > > > > > > > > > > > Roman Koriakov > > > > > > > > > > > Software Developer > > > > > > > > > > > Kirova 11, Voronezh, Russia > > > > > > > > > > > Tel: + 7 473 200 15 30 > > > > > > > > > > > E-mail: roman.koria...@t-systems.com > roman.koria...@t-systems.com<mailto:roman.koria...@t-systems.com% > > 3cmailto:roman.koria...@t-systems.com> > > > > > <mailto:roman.koria...@t-systems.com% > > 3cmailto:roman.koria...@t-systems.com > > > > > >> > > > > > > > > > > > http://www.t-systems.com<http://www.t-systems.ru/<< > > http://www.t-systems.com%3chttp:/www.t-systems.ru/%3c> > > > > > http://www.t-systems.com%3chttp:/www.t-systems.ru/>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Best regards, Ivan Pavlukhin

Re: [DISCUSS] dependencies and release process for Ignite Extensions

2019-12-10 Thread Ivan Pavlukhin
lying that the updated > > > >> extensions > > > >>will work for Ignite 2.9 and later until we need to update them > > again > > > >>creating a release branch like "ignite-core-2.14+" > > > >>- If only a subset of the extensions was updated then we need to > > > >> release > > > >>those extensions to Maven. The goal is to avoid the practice of > > > >> publishing > > > >>Flink or any other extension to Maven for every core release if > > there > > > >> are > > > >>no changes. > > > >>- As for a ZIP archive, we should prepare the archive for a > > download > > > >>with the name like "ignite-core-2.9+" > > > >> > > > >> > > > >> - > > > >> Denis > > > >> > > > >> > > > >> On Tue, Nov 26, 2019 at 9:03 PM Saikat Maitra < > > saikat.mai...@gmail.com> > > > >> wrote: > > > >> > > > >> > Hello, > > > >> > > > > >> > I wanted to connect and discuss on the release process for > > > >> > ignite-extensions. As of today all our integrations since released > > > >> together > > > >> > were able to run build based on latest snapshot for example the > > > current > > > >> > build depends on 2.8.0-SNAPSHOT. If we are making ignite-extensions > > as > > > >> > separate project with different release cycle then it make sense to > > > have > > > >> > dependencies on core modules based on released artifact for example > > > the > > > >> > dependency for ignite-core would be 2.7.6 > > > >> > > > > >> > Please review and share your thoughts. > > > >> > > > > >> > PR https://github.com/apache/ignite-extensions/pull/1 > > > >> > > > > >> > Regards > > > >> > Saikat > > > >> > > > > >> > > > > > > > > > -- Best regards, Ivan Pavlukhin

Re: Embedded Version of H2

2019-10-18 Thread Ivan Pavlukhin
A folow-up, there is an interesting ticket [1]. Need to check if window functions are covered. [1] https://issues.apache.org/jira/browse/IGNITE-7664 пт, 18 окт. 2019 г. в 10:01, Ivan Pavlukhin : > > Hi Steve, > > I am afraid that window functions and OVER keyword will not work >

Re: Embedded Version of H2

2019-10-18 Thread Ivan Pavlukhin
...@gmail.com : > > Hello, > > Actually I found the answer with the following ticket : > https://issues.apache.org/jira/browse/IGNITE-10801 > > Seems to be planned for 2.8.0 > > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ -- Best regards, Ivan Pavlukhin

Re: Broken image links in under-the-hood articles in wiki

2019-10-15 Thread Ivan Pavlukhin
ITE/Ignite+Durable+Memory+-+under+the+hood вт, 15 окт. 2019 г. в 17:34, Dmitriy Pavlov : > > Hi Ivan, > > thank you for doing all these changes. I've attached the last one. > > Sincerely, > Dmitriy Pavlov > > вт, 15 окт. 2019 г. в 15:56, Ivan Pavlukhin : > > > Dm

Re: Adding experimental support for Intel Optane DC Persistent Memory

2019-10-15 Thread Ivan Pavlukhin
lugeta of > Intel (both copied) think about this and other approaches. > > Ivan, I'm not sure if any performance testing was done for the given > pull-request. Anyway, it might be premature considering Alex's summary. > > - > Denis > > > On Mon, Oct 14, 2019 at 11:50 PM Ivan

Binary object format KB article

2019-10-16 Thread Ivan Pavlukhin
-- Best regards, Ivan Pavlukhin

Re: Binary object format KB article

2019-10-16 Thread Ivan Pavlukhin
/cwiki.apache.org/confluence/display/IGNITE/IEP-9+Thin+Client+Protocol#IEP-9ThinClientProtocol-BinaryObjects > > > > > > > > On Wed, Oct 16, 2019 at 11:49 AM Ivan Pavlukhin > > wrote: > > > > > Igniters, > > > > > > I published a document about

Re: Adding experimental support for Intel Optane DC Persistent Memory

2019-10-15 Thread Ivan Pavlukhin
;> >>> > > >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-26%3A+Adding+Ex > >> >>> > perimental+Support+for+Intel+Optane+DC+Persistent+Memory > >> >>> > > >> >>> > Sincerely, > >> >>> > Dmitriy Pavlov > >> >>> > > >> >>> > чт, 26 июл. 2018 г. в 15:31, Stanislav Lukyanov < > >> >>> stanlukya...@gmail.com>: > >> >>> > > >> >>> >> Ah, ok, it’s just the ‘.’ at the end of the link. Removed it and > >> it’s > >> >>> >> fine. > >> >>> >> > >> >>> >> From: Stanislav Lukyanov > >> >>> >> Sent: 26 июля 2018 г. 15:12 > >> >>> >> To: dev@ignite.apache.org > >> >>> >> Subject: RE: Adding experimental support for Intel Optane DC > >> >>> >> Persistent Memory > >> >>> >> > >> >>> >> Hi, > >> >>> >> > >> >>> >> The link you’ve shared gives me 404. > >> >>> >> Perhaps you need to add a permission for everyone to access the > >> page? > >> >>> >> > >> >>> >> Thanks, > >> >>> >> Stan > >> >>> >> > >> >>> >> From: Mammo, Mulugeta > >> >>> >> Sent: 26 июля 2018 г. 2:44 > >> >>> >> To: dev@ignite.apache.org > >> >>> >> Subject: Adding experimental support for Intel Optane DC Persistent > >> >>> >> Memory > >> >>> >> > >> >>> >> Hi, > >> >>> >> > >> >>> >> I have added a new proposal to support Intel Optane DC Persistent > >> >>> >> Memory for Ignite here: > >> >>> >> > >> https://cwiki.apache.org/confluence/display/IGNITE/Adding+Experimenta > >> >>> >> l+Support+for+Intel+Optane+DC+Persistent+Memory > >> >>> >> . > >> >>> >> > >> >>> >> I'm looking forward to your feedback and collaboration on this. > >> >>> >> > >> >>> >> Thanks, > >> >>> >> Mulugeta > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> >> > >> >>> > >> >> > >> > > -- Best regards, Ivan Pavlukhin

Re: [DISCUSS] PMC Chair rotation time

2019-10-22 Thread Ivan Pavlukhin
kind of dropped the ball on it > > > >> since. > > > >> > > > > >> > With that in mind, I offer my view on what a change in the Chair > > > >> > could > > > >> > offer: a renewed > > > >> > focus on community growth and development. If you agree with this > > > >> premise than > > > >> > somebody like Branko or Cos who could act as a forcing function to > > > >> constantly > > > >> > remind us about what else can we do to grow and develop this > > > >> > community > > > >> would > > > >> > be an ideal choice for the Chair (after all Branko's "tough love" was > > > >> > probably the > > > >> > most useful part of Ignite's experience in the Incubator). > > > >> > > > > >> > Now, of course, strictly speaking you don't have to be a Chair to do > > > >> > that. But lets > > > >> > face it -- that helps. And besides, a project's Chair doesn't really > > > >> > have any special > > > >> > powers when it comes to technological consensus, but anything that > > > >> > has > > > >> to do > > > >> > with external community the VP title that the chair gets can help > > > quite > > > >> a bit. > > > >> > > > > >> > Long story short: if Branko or Cos (as former mentors) would like to > > > >> > commit to 6 more > > > >> > months of the same hands-on mentorship focused on community > > > development > > > >> -- they > > > >> > would have my wholehearted support. > > > >> > > > > >> > Thanks, > > > >> > Roman (with my PMC member hat on). > > > >> > > > > > > > > > > > > > > > > > -- > > - > > Denis > > > > -- > Best Regards, Vyacheslav D. -- Best regards, Ivan Pavlukhin

Re: [DISCUSS] PMC Chair rotation time

2019-10-24 Thread Ivan Pavlukhin
t;>>> a little bit. > > > > > > >>>>> Note, that what I'm about to say is coming from a non-coding > > > (on > > > > > > >>>> Ignite) member > > > > > > >>>>> of the PMC. In fact, I stayed on the PMC after graduation > > more > > > > with > > > > > > my > > > > > > >>>> ASF > > > > > > >>>>> member hat on, rather than as somebody who wanted to directly > > > > > > >> contribute > > > > > > >>>>> to where the technology was going. My concern during your > > > > > incubation > > > > > > >>>> days > > > > > > >>>>> was (and still is!) how well are you guys doing on the > > > community > > > > > > >>>> development > > > > > > >>>>> front. > > > > > > >>>>> > > > > > > >>>>> If you recall, the diversity requirement (the fact that more > > > than > > > > > 80% > > > > > > >>>> of project > > > > > > >>>>> members work for the same company) came up during our > > > graduation. > > > > > > >> While > > > > > > >>>>> it wasn't a blocking requirement it still was a very valid > > > > concern. > > > > > > >>>> Monocultures > > > > > > >>>>> are really nasty for open source communities. > > > > > > >>>>> > > > > > > >>>>> I think it would be fair to say that Ignite community hasn't > > > > really > > > > > > >>>>> improved much > > > > > > >>>>> diversity-wise since its graduation. And I honestly feel that > > > > this > > > > > > is, > > > > > > >>>>> to a larger > > > > > > >>>>> extent, because the focus is now missing. It was well > > > understood > > > > > that > > > > > > >>>> in order > > > > > > >>>>> to graduate the community had to do all it can to > > demonstrate a > > > > > > >>>>> positive trajectory > > > > > > >>>>> in that direction. And we did. But we kind of dropped the > > ball > > > on > > > > > it > > > > > > >>>> since. > > > > > > >>>>> > > > > > > >>>>> With that in mind, I offer my view on what a change in the > > > Chair > > > > > > could > > > > > > >>>>> offer: a renewed > > > > > > >>>>> focus on community growth and development. If you agree with > > > this > > > > > > >>>> premise than > > > > > > >>>>> somebody like Branko or Cos who could act as a forcing > > function > > > > to > > > > > > >>>> constantly > > > > > > >>>>> remind us about what else can we do to grow and develop this > > > > > > community > > > > > > >>>> would > > > > > > >>>>> be an ideal choice for the Chair (after all Branko's "tough > > > love" > > > > > was > > > > > > >>>>> probably the > > > > > > >>>>> most useful part of Ignite's experience in the Incubator). > > > > > > >>>>> > > > > > > >>>>> Now, of course, strictly speaking you don't have to be a > > Chair > > > to > > > > > do > > > > > > >>>>> that. But lets > > > > > > >>>>> face it -- that helps. And besides, a project's Chair doesn't > > > > > really > > > > > > >>>>> have any special > > > > > > >>>>> powers when it comes to technological consensus, but anything > > > > that > > > > > > has > > > > > > >>>> to do > > > > > > >>>>> with external community the VP title that the chair gets can > > > help > > > > > > >> quite > > > > > > >>>> a bit. > > > > > > >>>>> > > > > > > >>>>> Long story short: if Branko or Cos (as former mentors) would > > > like > > > > > to > > > > > > >>>>> commit to 6 more > > > > > > >>>>> months of the same hands-on mentorship focused on community > > > > > > >> development > > > > > > >>>> -- they > > > > > > >>>>> would have my wholehearted support. > > > > > > >>>>> > > > > > > >>>>> Thanks, > > > > > > >>>>> Roman (with my PMC member hat on). > > > > > > >>>> > > > > > > >>> > > > > > > >>> > > > > > > >> > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > - > > > > > > > Denis > > > > > > > > > > > > > > > > > > > > -- Best regards, Ivan Pavlukhin

Re: [DISCUSS] PMC Chair rotation time

2019-10-24 Thread Ivan Pavlukhin
> Sorry to come to this thread rather late, but I wanted to > > > > offer a > > > > > > > >>>> somewhat > > > > > > > >>>>> different perspective that hopefully can help reframe this > > > > > > discussion > > > > > > > >>>>> a little bit. > > > > > > > >>>>> Note, that what I'm about to say is coming from a > > non-coding > > > > (on > > > > > > > >>>> Ignite) member > > > > > > > >>>>> of the PMC. In fact, I stayed on the PMC after graduation > > > more > > > > > with > > > > > > > my > > > > > > > >>>> ASF > > > > > > > >>>>> member hat on, rather than as somebody who wanted to > > directly > > > > > > > >> contribute > > > > > > > >>>>> to where the technology was going. My concern during your > > > > > > incubation > > > > > > > >>>> days > > > > > > > >>>>> was (and still is!) how well are you guys doing on the > > > > community > > > > > > > >>>> development > > > > > > > >>>>> front. > > > > > > > >>>>> > > > > > > > >>>>> If you recall, the diversity requirement (the fact that > > more > > > > than > > > > > > 80% > > > > > > > >>>> of project > > > > > > > >>>>> members work for the same company) came up during our > > > > graduation. > > > > > > > >> While > > > > > > > >>>>> it wasn't a blocking requirement it still was a very valid > > > > > concern. > > > > > > > >>>> Monocultures > > > > > > > >>>>> are really nasty for open source communities. > > > > > > > >>>>> > > > > > > > >>>>> I think it would be fair to say that Ignite community > > hasn't > > > > > really > > > > > > > >>>>> improved much > > > > > > > >>>>> diversity-wise since its graduation. And I honestly feel > > that > > > > > this > > > > > > > is, > > > > > > > >>>>> to a larger > > > > > > > >>>>> extent, because the focus is now missing. It was well > > > > understood > > > > > > that > > > > > > > >>>> in order > > > > > > > >>>>> to graduate the community had to do all it can to > > > demonstrate a > > > > > > > >>>>> positive trajectory > > > > > > > >>>>> in that direction. And we did. But we kind of dropped the > > > ball > > > > on > > > > > > it > > > > > > > >>>> since. > > > > > > > >>>>> > > > > > > > >>>>> With that in mind, I offer my view on what a change in the > > > > Chair > > > > > > > could > > > > > > > >>>>> offer: a renewed > > > > > > > >>>>> focus on community growth and development. If you agree > > with > > > > this > > > > > > > >>>> premise than > > > > > > > >>>>> somebody like Branko or Cos who could act as a forcing > > > function > > > > > to > > > > > > > >>>> constantly > > > > > > > >>>>> remind us about what else can we do to grow and develop > > this > > > > > > > community > > > > > > > >>>> would > > > > > > > >>>>> be an ideal choice for the Chair (after all Branko's "tough > > > > love" > > > > > > was > > > > > > > >>>>> probably the > > > > > > > >>>>> most useful part of Ignite's experience in the Incubator). > > > > > > > >>>>> > > > > > > > >>>>> Now, of course, strictly speaking you don't have to be a > > > Chair > > > > to > > > > > > do > > > > > > > >>>>> that. But lets > > > > > > > >>>>> face it -- that helps. And besides, a project's Chair > > doesn't > > > > > > really > > > > > > > >>>>> have any special > > > > > > > >>>>> powers when it comes to technological consensus, but > > anything > > > > > that > > > > > > > has > > > > > > > >>>> to do > > > > > > > >>>>> with external community the VP title that the chair gets > > can > > > > help > > > > > > > >> quite > > > > > > > >>>> a bit. > > > > > > > >>>>> > > > > > > > >>>>> Long story short: if Branko or Cos (as former mentors) > > would > > > > like > > > > > > to > > > > > > > >>>>> commit to 6 more > > > > > > > >>>>> months of the same hands-on mentorship focused on community > > > > > > > >> development > > > > > > > >>>> -- they > > > > > > > >>>>> would have my wholehearted support. > > > > > > > >>>>> > > > > > > > >>>>> Thanks, > > > > > > > >>>>> Roman (with my PMC member hat on). > > > > > > > >>>> > > > > > > > >>> > > > > > > > >>> > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > - > > > > > > > > Denis > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Best regards, Ivan Pavlukhin

Re: Unclear to use methods in the DiscoverySpiCustomMessage interface

2019-10-25 Thread Ivan Pavlukhin
not be > > used because may not be supported depending on the configuration. > > Perhaps some functionality that uses it is not working correctly with > > zookeeper configured. It seems we should avoid it in the custom > > message interface too. > > > > WDYT? > > > > -- > > Best wishes, > > Amelchev Nikita > > -- Best regards, Ivan Pavlukhin

Re: Ignite in 2019: Status and Directions

2019-10-25 Thread Ivan Pavlukhin
lopers. Ignite is your and our project, come out of the building and >tell of your work proudly. > > > Sorry for a long story, share your thoughts. > > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-PMC-Chair-rotation-time-td11941.html > > - > Denis -- Best regards, Ivan Pavlukhin

Re: [DISCUSS] Proposal for Ignite Extensions as a separate Bahir module or Incubator project

2019-10-28 Thread Ivan Pavlukhin
move > >> > > > > > > > > Ignite-Kafka, > >> > > > > > > > > > > > Ignite-Camel to a separate project specially > >> intended > >> > for > >> > > > > > > > > integration. > >> > > > > > > > > > > > > >> > > > > > > > > > > > So if we stay with option 1 I would be glad to help. > >> > > Count > >> > > > on > >> > > > > > my > >> > > > > > > > > > support > >> > > > > > > > > > > > within the migration to Apache Bahir. Inter-project > >> > > > > interaction > >> > > > > > > and > >> > > > > > > > > > > > integration are usually welcomed in the ASF. > >> > > > > > > > > > > > > >> > > > > > > > > > > > Sincerely, > >> > > > > > > > > > > > Dmitriy Pavlov > >> > > > > > > > > > > > > >> > > > > > > > > > > > ср, 23 окт. 2019 г. в 09:31, Alexey Zinoviev < > >> > > > > > > > zaleslaw@gmail.com > >> > > > > > > > > >: > >> > > > > > > > > > > > > >> > > > > > > > > > > > > Also, dear Saikat Maitra, could you please > >> describe > >> > how > >> > > > you > >> > > > > > see > >> > > > > > > > the > >> > > > > > > > > > > > > release cycles in Bahir Ignite Extensions and how > >> it > >> > be > >> > > > > > related > >> > > > > > > > to > >> > > > > > > > > > > Ignite > >> > > > > > > > > > > > > release, 2.9, 3.0 for example. > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > Thank you for your energy > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > ср, 23 окт. 2019 г., 8:10 Alexey Zinoviev < > >> > > > > > > > zaleslaw@gmail.com > >> > > > > > > > > >: > >> > > > > > > > > > > > > > >> > > > > > > > > > > > >> Please, give me permissions too, I'd glad to help > >> > with > >> > > > > this > >> > > > > > > > > modules > >> > > > > > > > > > > > >> migration and support part of them in future, but > >> > also > >> > > > we > >> > > > > > need > >> > > > > > > > not > >> > > > > > > > > > > only > >> > > > > > > > > > > > >> contributor but a few Committer permissions to > >> merge > >> > > In > >> > > > > > > > repository > >> > > > > > > > > > in > >> > > > > > > > > > > > other > >> > > > > > > > > > > > >> side it could be very long proccess. > >> > > > > > > > > > > > >> > >> > > > > > > > > > > > >> Could you ask Bahir Community about that? > >> > > > > > > > > > > > >> > >> > > > > > > > > > > > >> ср, 23 окт. 2019 г., 2:31 Saikat Maitra < > >> > > > > > > > saikat.mai...@gmail.com > >> > > > > > > > > >: > >> > > > > > > > > > > > >> > >> > > > > > > > > > > > >>> Hi, > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> I discussed with Apache Bahir community and they > >> > are > >> > > > > > > interested > >> > > > > > > > > to > >> > > > > > > > > > > have > >> > > > > > > > > > > > >>> Apache Ignite extensions as part of Apache Bahir > >> > > > project. > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> I have also requested for contributor access in > >> > Jira > >> > > > for > >> > > > > > > Apache > >> > > > > > > > > > Bahir > >> > > > > > > > > > > > >>> project so that I can create issues and assign > >> to > >> > > > > myself. I > >> > > > > > > can > >> > > > > > > > > > help > >> > > > > > > > > > > > with > >> > > > > > > > > > > > >>> code reviews as well. > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> Also my thoughts on releases specific to > >> > dependencies > >> > > > for > >> > > > > > > > Apache > >> > > > > > > > > > > Ignite > >> > > > > > > > > > > > >>> is > >> > > > > > > > > > > > >>> to do a fast follow up release for modules > >> based on > >> > > > > latest > >> > > > > > > > Apache > >> > > > > > > > > > > > Ignite > >> > > > > > > > > > > > >>> stable release. > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> Here is the email thread for reference > >> > > > > > > > > > > > >>> > >> > > > > > > > > >> > https://www.mail-archive.com/dev@bahir.apache.org/msg02703.html > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> I wanted to connect and get feedback on the > >> > proposal > >> > > > and > >> > > > > if > >> > > > > > > we > >> > > > > > > > > are > >> > > > > > > > > > ok > >> > > > > > > > > > > > to > >> > > > > > > > > > > > >>> move the following Apache Ignite Extensions > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> Regards, > >> > > > > > > > > > > > >>> Saikat > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> On Fri, Oct 18, 2019 at 9:44 PM Saikat Maitra < > >> > > > > > > > > > > saikat.mai...@gmail.com > >> > > > > > > > > > > > > > >> > > > > > > > > > > > >>> wrote: > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >>> > Hello, > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > We wanted to discuss on a proposal to move and > >> > > > support > >> > > > > > the > >> > > > > > > > > Apache > >> > > > > > > > > > > > >>> Ignite > >> > > > > > > > > > > > >>> > integrations as separate Ignite Extensions as > >> > > > discussed > >> > > > > > > here > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Pub-Sub-Streamer-Implementation-td43944.html > >> > > > > > > > > > > > >>> > . > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > The reason we wanted to move our Apache Ignite > >> > > > > > integration > >> > > > > > > as > >> > > > > > > > > > > > separate > >> > > > > > > > > > > > >>> > Extensions is this will help us to manage and > >> > > > maintain > >> > > > > > > > separate > >> > > > > > > > > > > > >>> lifecycle > >> > > > > > > > > > > > >>> > for Apache Ignite integrations. > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > All the integrations will continue to be part > >> of > >> > > ASF > >> > > > > and > >> > > > > > we > >> > > > > > > > > will > >> > > > > > > > > > > > keep > >> > > > > > > > > > > > >>> > supporting and developing in accordance with > >> ASF > >> > > > vision > >> > > > > > and > >> > > > > > > > > > > > practices. > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > We are considering following two choices for > >> > moving > >> > > > to > >> > > > > > > Apache > >> > > > > > > > > > > Ignite > >> > > > > > > > > > > > >>> > Extensions: > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > 1. Reach out to Apache Bahir community and > >> > propose > >> > > to > >> > > > > > make > >> > > > > > > > > Ignite > >> > > > > > > > > > > > >>> > Extensions a separate module as part of Apache > >> > > Bahir > >> > > > > > > project. > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > https://bahir.apache.org/ > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces96 > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > 2. Reach out to Apache Incubator community and > >> > > > request > >> > > > > > for > >> > > > > > > a > >> > > > > > > > > new > >> > > > > > > > > > > > >>> project > >> > > > > > > > > > > > >>> > for Ignite Extensions. > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > Please review and share feedback on our > >> proposal. > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > Warm Regards, > >> > > > > > > > > > > > >>> > Saikat > >> > > > > > > > > > > > >>> > > >> > > > > > > > > > > > >>> > >> > > > > > > > > > > > >> > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > > -- Best regards, Ivan Pavlukhin

Re: [VOTE] Apache Ignite PMC Chair

2019-10-28 Thread Ivan Pavlukhin
r 1st, > > > 11:00 AM Pacific Time. More details about the next steps are here: > > > https://www.apache.org/dev/pmc.html#newchair > > > > > > - > > > Denis > > > -- Best regards, Ivan Pavlukhin

Re: Ignite-Spark integration meeting

2019-10-23 Thread Ivan Pavlukhin
Correction. How are you going to TEST integrations with different Spark versions? ср, 23 окт. 2019 г. в 15:16, Ivan Pavlukhin : > > Alexey, > > Thank you for sharing the summary! > > Small question. How are you going to integrations with different Spark > versions? > &g

Re: Ignite-Spark integration meeting

2019-10-23 Thread Ivan Pavlukhin
[Spark] Add initial support of Spark 2.4 > > >> > <https://issues.apache.org/jira/browse/IGNITE-12247> > > >> > 3. [Spark] Add joins to Spark Dataframe examples > > >> > <https://issues.apache.org/jira/browse/IGNITE-9732> > > >> > > > >> > > > >> >- Known issues of migration to 2.4 version > > >> >- Organization of multiple version support for Apache Spark > > >> > > > >> > P.S. meeting notes will be shared with the community > > >> > P.P.S Nikolay, if you have any objections about the time or topics, > > >> please > > >> > let me know > > >> > > > > > -- Best regards, Ivan Pavlukhin

Re: Ignite-Spark integration meeting

2019-10-23 Thread Ivan Pavlukhin
Actually, I meant running tests on TeamCity. ср, 23 окт. 2019 г. в 15:36, Alexey Zinoviev : > > What kind of testing do you mean? JUnit, integration via example or > something else? > > ср, 23 окт. 2019 г., 14:16 Ivan Pavlukhin : > > > Correction. > > > > Ho

Re: Adding experimental support for Intel Optane DC Persistent Memory

2019-10-16 Thread Ivan Pavlukhin
> - > Denis > > > On Tue, Oct 15, 2019 at 10:44 PM Ivan Pavlukhin wrote: > > > Denis, > > > > I suppose we are using not optimal strategy here. And motivation is simple: > > 1. Code review is "expensive", benchmarking (usually) are "ch

Re: Binary object format KB article

2019-10-16 Thread Ivan Pavlukhin
aspects of this functionality leak into the explanation and > confuses reader. > > On Wed, Oct 16, 2019 at 2:52 PM Ivan Pavlukhin wrote: > > > Pavel, Sergey, > > > > Thank you for your feedback! > > > > To be exact the document does not describe broad pic

Re: Broken image links in under-the-hood articles in wiki

2019-10-15 Thread Ivan Pavlukhin
hannel. > > I didn't manage to do it on the weekend, but this change is on my list. > > пн, 14 окт. 2019 г. в 18:23, Ivan Pavlukhin : > > > Dmitriy, > > > > > PS, I've shared links to new images sources in the Slack channel. > > > > Cannot find links

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-11-26 Thread Ivan Pavlukhin
oper > > >> sorting > > >> >> of Lucene index response and correct reducing of them for distributed > > >> >> queries. > > >> >> > > >> >> *There are two Lucene based aspects* > > >>

Re: Data consistency essentials explained

2019-11-30 Thread Ivan Pavlukhin
- code highlight, fonts, etc. > > > > For now, it’s very hard to read it. > > > > Can you, please, do it? > > > > > 28 нояб. 2019 г., в 09:25, Ivan Pavlukhin > > написал(а): > > > > > > Alexei, > > > > > > Many t

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-12-02 Thread Ivan Pavlukhin
And is the problem specific to range queries or not? пн, 2 дек. 2019 г. в 11:12, Ivan Pavlukhin : > > Yuriy, > > Thank you for investigating the problem [1]. Still cannot realize how > the problem relates to introduced "limit"? Is it right that there were > no dupli

Re: Re: Joining node validation failure event.

2019-12-01 Thread Ivan Pavlukhin
idation > >>>> failure > >>>> in Ignite components and obtain information of the node that tried to > >>>> join and the reason for the failure. Now, as I see, there is no way to > >>>> do it. I propose to implement a new event -- NodeValidationFailedEvent > >>>> -- and record it in case the validation fails. I have created Tiket [1] > >>>> and PR [2], which shows an example of implementation. Could anyone take > >>>> a look at it, please? > >>>> > >>>> [1] https://issues.apache.org/jira/browse/IGNITE-12380 > >>>> > >>>> [2] https://github.com/apache/ignite/pull/7057 > >>>> -- Best regards, Ivan Pavlukhin

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-12-02 Thread Ivan Pavlukhin
tries multiple times. > > Please check the issue https://issues.apache.org/jira/browse/IGNITE-12401 > and corresponding build > https://ci.ignite.apache.org/viewQueued.html?itemId=4799634 > > Regards, > -- > Ilya Kasnacheev -- Best regards, Ivan Pavlukhin

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-12-02 Thread Ivan Pavlukhin
y are broken now, but now even a simple "token in field > with limit" returns duplicates. > > Before limits were introduced, any tested use cases were unaffected by > duplicates, but now they are. > > Regards, > -- > Ilya Kasnacheev > > > пн, 2 дек. 2019 г.

Re: [RESULT] Ignite PMC Chair Vote

2019-11-21 Thread Ivan Pavlukhin
iy, congratulations! > > > > > > > > > > > > > > > > On 7 Nov 2019, at 12:06, Николай Кулагин > > > > > wrote: > > > > > > > > > > > > Dmitry, my congratulations! > > > > > > >

Re: Joining node validation failure event.

2019-11-27 Thread Ivan Pavlukhin
-- NodeValidationFailedEvent > >> -- and record it in case the validation fails. I have created Tiket [1] > >> and PR [2], which shows an example of implementation. Could anyone take > >> a look at it, please? > >> > >> [1] https://issues.apache.org/jira/browse/IGNITE-12380 > >> > >> [2] https://github.com/apache/ignite/pull/7057 > >> -- Best regards, Ivan Pavlukhin

Re: Data consistency essentials explained

2019-11-27 Thread Ivan Pavlukhin
r IGNITE-10780 and several follow-up fixes. >> >> There is still work to be done. Currently I'm working on similar issue for >> atomic persistent caches [2]. I hope to give an update on that soon. >> >> [1] https://cwiki.apache.org/confluence/display/IGNITE/Data+consistency >> [2] https://issues.apache.org/jira/browse/IGNITE-11797 >> -- >> >> Best regards, >> Alexei Scherbakov -- Best regards, Ivan Pavlukhin

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-11-28 Thread Ivan Pavlukhin
Folks, Yuriy, I suppose that we are going to proceed with >>> Reducing on Ignite The obvious point of distributed response reduction is class GridCacheDistributedQueryFuture. Though, @Ivan Pavlukhin mentioned class with similar functionality: ReduceIndexSorted What I

Re: Calcite based SQL query engine. Local queries

2019-11-01 Thread Ivan Pavlukhin
; non-co-located caches inside a single query fragment (result of local query > > planning is a single query fragment). So, we cannot pass the check. > > > > > > Should we throw an exception or omit the check for local query planning > > or prohibit local queries at all? > > > > > > Your thoughts? > > > > > > Regards, > > > Igor > > -- Best regards, Ivan Pavlukhin

Re: Calcite based SQL query engine. Local queries

2019-11-01 Thread Ivan Pavlukhin
rimary reason why we > improved our affinityRuns ensuring no partition is purged from a node until > a task is completed is because many users were running local SQL from > compute tasks and needed a guarantee that SQL will always return a correct > result set. > > - > Denis >

Re: [MEETUP] 03.12.2019 Moscow

2019-11-28 Thread Ivan Pavlukhin
te, what I want in Ignite, what in Ignite are piss me > > off" > > > > Please, note, the language of the meetup is Russian. > > > > You should register here - > > https://www.meetup.com/ru-RU/Moscow-Apache-Ignite-Meetup/events/266728326 -- Best regards, Ivan Pavlukhin

Re: Enabling the checkstyle profile on Build Apache Ignite suite (test period)

2019-10-07 Thread Ivan Pavlukhin
branches. > > > > > > Any objections? > > > > > > [1] > > http://apache-ignite-developers.2346864.n4.nabble.com/Code-inspection-td27709i80.html#a41297 -- Best regards, Ivan Pavlukhin

Broken image links in under-the-hood articles in wiki

2019-10-09 Thread Ivan Pavlukhin
ce/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood -- Best regards, Ivan Pavlukhin

Re: Replacing default work dir from tmp to current dir

2019-10-04 Thread Ivan Pavlukhin
> > have any distrubted features. > > > > > > > > > > See no difference here. Imagine a user starts only one Ignite node > > for > > > > > development or just to play (which, I believe, happes quite a lot) - > > > same > > > > > as with local databases. BTW, it is impossible to start SQLite > > without > > > > > database path, so a user either provides a full path, or a relative > > > path > > > > > from the current directory - which is an explicit action from a user. > > > > > > > > > > > > > > > > I agree with you. > > > > > > How it happens, that after wide discussion we implemented, reviewed > > > and > > > > > > merged wrong defaults? > > > > > > > > > > > > As I know, we have explicit release only to change this default. > > > > > > > > > > > > This release is broken, isn't it? > > > > > > > > > > > I think this is just a miscommunication. Ilya made a fix which was > > > > exactly > > > > > what he meant it to be. As for the release - it may have worse > > > usability, > > > > > but not more 'broken' as the previous one with the temp directory. At > > > > least > > > > > the data will not be physically removed after the machine restart. > > > > > > > > > > > > > > -- Best regards, Ivan Pavlukhin

Re: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-10-04 Thread Ivan Pavlukhin
> > > > first > > > > > > > > > > > > page is sent to client? > > > > > > > > > > > > > > > > > > > > > > > > I'd think a new parameter should be added to limit > > > result. > > > > The > > > > > > best > > > > > > > > > > > > solution is to use query language commands for this, > > e.g. > > > > > > > > > > "LIMIT/OFFSET" > > > > > > > > > > > in > > > > > > > > > > > > SQL. > > > > > > > > > > > > > > > > > > > > > > > > This task doesn't look trivial. Query is distributed > > > > operation > > > > > > and > > > > > > > > > same > > > > > > > > > > > > user query will be executed on data nodes > > > > > > > > > > > > and then results from all nodes should be correcly > > merged > > > > > > before > > > > > > > > > being > > > > > > > > > > > > returned via client-cursor. > > > > > > > > > > > > So, LIMIT should be applied on every node and then on > > > merge > > > > > > phase. > > > > > > > > > > > > > > > > > > > > > > > > Also, this may be non-obviuos, limiting results make no > > > > sence > > > > > > > > without > > > > > > > > > > > > sorting, > > > > > > > > > > > > as there is no guarantee every next query run will > > return > > > > same > > > > > > data > > > > > > > > > > > because > > > > > > > > > > > > of page reordeing. > > > > > > > > > > > > Basically, merge phase receive results from data nodes > > > > > > > > asynchronously > > > > > > > > > > and > > > > > > > > > > > > messages from different nodes can't be ordered. > > > > > > > > > > > > > > > > > > > > > > > > 2. > > > > > > > > > > > > a. "tokenize" param name (for @QueryTextFiled) looks > > more > > > > > > verbose, > > > > > > > > > > isn't > > > > > > > > > > > > it. > > > > > > > > > > > > b,c. What about distributed query? How partial results > > > from > > > > > > nodes > > > > > > > > > will > > > > > > > > > > be > > > > > > > > > > > > merged? > > > > > > > > > > > > Does Lucene allows to configure comparator for data > > > > sorting? > > > > > > > > > > > > What comparator Ignite should choose to sort result on > > > > merge > > > > > > phase? > > > > > > > > > > > > > > > > > > > > > > > > 3. For now Lucene engine is not configurable at all. > > E.g. > > > > it is > > > > > > > > > > > impossible > > > > > > > > > > > > to configure Tokenizer. > > > > > > > > > > > > I'd think about possible ways to configure engine at > > > first > > > > and > > > > > > only > > > > > > > > > > then > > > > > > > > > > > go > > > > > > > > > > > > further to discuss\implement complex features, > > > > > > > > > > > > that may depends on engine config. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Aug 29, 2019 at 8:17 PM Yuriy Shuliga < > > > > > > shul...@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Dear community, > > > > > > > > > > > > > > > > > > > > > > > > > > By starting this chain I'd like to open discussion > > that > > > > would > > > > > > > > come > > > > > > > > > to > > > > > > > > > > > > > contribution results in subj. area. > > > > > > > > > > > > > > > > > > > > > > > > > > Ignite has indexing capabilities, backed up by > > > different > > > > > > > > > mechanisms, > > > > > > > > > > > > > including Lucene. > > > > > > > > > > > > > > > > > > > > > > > > > > Currently, Lucene 7.5.0 is used (past year release). > > > > > > > > > > > > > This is a wide spread and mature technology that > > covers > > > > text > > > > > > > > search > > > > > > > > > > > area > > > > > > > > > > > > > and beyond (e.g. spacial data indexing). > > > > > > > > > > > > > > > > > > > > > > > > > > My goal is to *expose more Lucene functionality to > > > Ignite > > > > > > > > indexing > > > > > > > > > > and > > > > > > > > > > > > > query mechanisms for text data*. > > > > > > > > > > > > > > > > > > > > > > > > > > It's quite simple request at current stage. It is > > > coming > > > > > > from our > > > > > > > > > > > > project's > > > > > > > > > > > > > needs, but i believe, will be useful for a lot more > > > > people. > > > > > > > > > > > > > Let's walk through and vote or discuss about Jira > > > > tickets for > > > > > > > > them. > > > > > > > > > > > > > > > > > > > > > > > > > > 1.[trivial] Use dataQuery.getPageSize() to limit > > > search > > > > > > > > response > > > > > > > > > > > items > > > > > > > > > > > > > inside GridLuceneIndex.query(). Currently it is > > calling > > > > > > > > > > > > > IndexSearcher.search(query, *Integer.MAX_VALUE*) - so > > > > > > basically > > > > > > > > all > > > > > > > > > > > > scored > > > > > > > > > > > > > matches will me returned, what we do not need in most > > > > cases. > > > > > > > > > > > > > > > > > > > > > > > > > > 2.[simple] Add sorting. Then more capable search > > call > > > > can be > > > > > > > > > > > > > executed: *IndexSearcher.search(query, count, > > > > > > > > > > > > > sort) * > > > > > > > > > > > > > Implementation steps: > > > > > > > > > > > > > a) Introduce boolean *sortField* parameter in > > > > > > *@QueryTextFiled * > > > > > > > > > > > > > annotation. If > > > > > > > > > > > > > *true *the filed will be indexed but not tokenized. > > > > Number > > > > > > types > > > > > > > > > are > > > > > > > > > > > > > preferred here. > > > > > > > > > > > > > b) Add *sort* collection to *TextQuery* constructor. > > It > > > > > > should > > > > > > > > > define > > > > > > > > > > > > > desired sort fields used for querying. > > > > > > > > > > > > > c) Implement Lucene sort usage in > > > > GridLuceneIndex.query(). > > > > > > > > > > > > > > > > > > > > > > > > > > 3.[moderate] Build complex queries with *TextQuery*, > > > > > > including > > > > > > > > > > > > > terms/queries boosting. > > > > > > > > > > > > > *This section for voting only, as requires more > > > detailed > > > > > > work. > > > > > > > > > Should > > > > > > > > > > > be > > > > > > > > > > > > > extended if community is interested in it.* > > > > > > > > > > > > > > > > > > > > > > > > > > Looking forward to your comments! > > > > > > > > > > > > > > > > > > > > > > > > > > BR, > > > > > > > > > > > > > Yuriy Shuliha > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Best regards, > > > > > > > > > > > > Andrey V. Mashenkov > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > Alexei Scherbakov > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Best regards, > > > > > > Ivan Pavlukhin > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Ivan Pavlukhin > > > > > > > > > > > > -- > Best regards, > Andrey V. Mashenkov -- Best regards, Ivan Pavlukhin

Re: New SQL execution engine

2019-10-04 Thread Ivan Pavlukhin
Nikolay, Guys updated IEP [1]. Could you please check it? Are there any missing parts needed at that stage? [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine вт, 1 окт. 2019 г. в 12:19, Ivan Pavlukhin : > > Folks, > > I marked IEP-33 as ob

Re: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

2019-10-04 Thread Ivan Pavlukhin
imit* solves the problem of redundant response > size. Without it *ALL* off the records are fetched each time; that is not > good, especially for loose patterns. > In order to solve relevance issue correct sorting should be implemented. > > Y. > > пт, 4 жовт. 2019 о 10:45 Ivan Pavlu

Re: Replacing default work dir from tmp to current dir

2019-10-03 Thread Ivan Pavlukhin
As for .NET. Should not we define IGNITE_HOME for it? чт, 3 окт. 2019 г. в 12:13, Ivan Pavlukhin : > > Folks, > > I am with Ilya here. I remind that we are talking not about general > case for Ignite usage. Generally IGNITE_HOME should be defined. > Otherwise we fal

Re: Replacing default work dir from tmp to current dir

2019-10-03 Thread Ivan Pavlukhin
> >> > > > > > > > > > That's why you have /usr/local/bin , > > > > /usr/local/sbin > > > > > >> > > > > > > > /usr/local/include etc... > > > > > >> > > > > > > > > > /opt on the other hand is for software that > > > doesn't > > > > > >> follow > > > > > >> > > > this > > > > > >> > > > > > and > > > > > >> > > > > > > > is deployed in a monolithic fashion. This usually > > > > includes > > > > > >> > > > commercial > > > > > >> > > > > > > > and/or cross-platform software that is packaged in > > the > > > > > >> > "Windows" > > > > > >> > > > > > style. " > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > >> Понедельник, 26 августа 2019, 22:49 +03:00 от > > > Denis > > > > > >> Magda > > > > > >> > < > > > > > >> > > > > > > > dma...@apache.org>: > > > > > >> > > > > > > > > >> > > > > > >> > > > > > > > > >> Igniters, > > > > > >> > > > > > > > > >> > > > > > >> > > > > > > > > >> I can't disagree with Nikolay that, as a > > > database, > > > > > >> Ignite > > > > > >> > > > needs > > > > > >> > > > > to > > > > > >> > > > > > > > persist > > > > > >> > > > > > > > > >> changes to a folder different from "user.home" > > > one. > > > > > But > > > > > >> > with > > > > > >> > > > the > > > > > >> > > > > > > > current > > > > > >> > > > > > > > > >> rate of project growth and adoption, I would > > > > > encourage > > > > > >> us > > > > > >> > to > > > > > >> > > > > > > > eliminate any > > > > > >> > > > > > > > > >> possible obstacles a user might come across > > > during > > > > > the > > > > > >> > > getting > > > > > >> > > > > > > started > > > > > >> > > > > > > > > >> phase with Ignite. Unfortunately, folders > > > different > > > > > >> from > > > > > >> > > > > > "user.home" > > > > > >> > > > > > > > imply > > > > > >> > > > > > > > > >> a significant restriction - the user needs to > > > allow > > > > > >> access > > > > > >> > > to > > > > > >> > > > > > > folders > > > > > >> > > > > > > > like > > > > > >> > > > > > > > > >> /lib, /etc; which can make every getting > > started > > > > demo > > > > > >> or > > > > > >> > app > > > > > >> > > > > fail. > > > > > >> > > > > > > > > >> > > > > > >> > > > > > > > > >> Thus, today, I'm casting my vote for > > > > > >> > "user.home"/ignite/work > > > > > >> > > > > > > > directory. > > > > > >> > > > > > > > > >> Please don't forget about Windows and MacOS. > > > > > >> > > > > > > > > >> > > > > > >> > > > > > > > > >> - > > > > > >> > > > > > > > > >> Denis > > > > > >> > > > > > > > > >> > > > > > >> > > > > > > > > >> > > > > > >> > > > > > > > > >> On Mon, Aug 26, 2019 at 7:09 AM Pavel Tupitsyn > > < > > > > > >> > > > > > > ptupit...@apache.org > > > > > >> > > > > > > > > wrote: > > > > > >> > > > > > > > > >> > > > > > >> > > > > > > > > >>> +1 for ~/.ignite/work > > > > > >> > > > > > > > > >>> > > > > > >> > > > > > > > > >>> As Petr mentioned above, this translates well > > to > > > > > >> Windows > > > > > >> > > and > > > > > >> > > > > > MacOS > > > > > >> > > > > > > > too, we > > > > > >> > > > > > > > > >>> can use "home directory" term in documentation > > > and > > > > > it > > > > > >> > works > > > > > >> > > > for > > > > > >> > > > > > any > > > > > >> > > > > > > > OS. > > > > > >> > > > > > > > > >>> > > > > > >> > > > > > > > > >>> On Mon, Aug 26, 2019 at 4:03 PM Nikolay > > Izhikov > > > < > > > > > >> > > > > > > > nizhi...@apache.org > > > > > > >> > > > > > > > > >>> wrote: > > > > > >> > > > > > > > > >>> > > > > > >> > > > > > > > > >>>> AFAIK server admin expects software will > > store > > > > it's > > > > > >> data > > > > > >> > > in > > > > > >> > > > > > /var/ > > > > > >> > > > > > > > > >>>> directory, not in /home directory. > > > > > >> > > > > > > > > >>>> > > > > > >> > > > > > > > > >>>>> In Docker age, packages are becoming > > extinct. > > > > > >> > > > > > > > > >>>> > > > > > >> > > > > > > > > >>>> I don't agree with that, but seems, it's not > > a > > > > > >> subject > > > > > >> > of > > > > > >> > > > > > > > discussion. :) > > > > > >> > > > > > > > > >>>> > > > > > >> > > > > > > > > >>>>> we don't even have very good packages today > > > > > >> > > > > > > > > >>>> > > > > > >> > > > > > > > > >>>> Why do you think we don't have good packages? > > > > > >> > > > > > > > > >>>> What is wrong with the current one? > > > > > >> > > > > > > > > >>>> > > > > > >> > > > > > > > > >>>>> I also think we should not copy what other > > > DBMS > > > > do > > > > > >> > since > > > > > >> > > > > their > > > > > >> > > > > > > > > >>>> ease-of-use > > > > > >> > > > > > > > > >>>>> is usually lacking > > > > > >> > > > > > > > > >>>> > > > > > >> > > > > > > > > >>>> We should define 'easy-of-use' here. > > > > > >> > > > > > > > > >>>> My experience with the modern dbms(postgres > > and > > > > > >> mysql) > > > > > >> > is > > > > > >> > > > > > > different. > > > > > >> > > > > > > > > >>>> > > > > > >> > > > > > > > > >>>> > > > > > >> > > > > > > > > >>>> В Пн, 26/08/2019 в 15:47 +0300, Ilya > > Kasnacheev > > > > > >> пишет: > > > > > >> > > > > > > > > >>>>> Hello! > > > > > >> > > > > > > > > >>>>> > > > > > >> > > > > > > > > >>>>> I think it is 2., because if a node is run > > > from > > > > > >> Ignite > > > > > >> > > > binary > > > > > >> > > > > > > > > >>>> distribution > > > > > >> > > > > > > > > >>>>> it has its root as a ignite work directory. > > I > > > > > think > > > > > >> it > > > > > >> > it > > > > > >> > > > > > another > > > > > >> > > > > > > > > >>>> argument > > > > > >> > > > > > > > > >>>>> for keeping data under current dir - Ignite > > > > binary > > > > > >> > > > > distribution > > > > > >> > > > > > > > already > > > > > >> > > > > > > > > >>>>> does it, why should embedded scenario be > > > > > different? > > > > > >> > > > > > > > > >>>>> > > > > > >> > > > > > > > > >>>>> In Docker age, packages are becoming > > extinct. > > > > > Nobody > > > > > >> > > wants > > > > > >> > > > > them > > > > > >> > > > > > > > > >>> anymore, > > > > > >> > > > > > > > > >>>>> anyway. I don't see why we should aim for > > > those > > > > > >> since > > > > > >> > we > > > > > >> > > > > don't > > > > > >> > > > > > > even > > > > > >> > > > > > > > > >>> have > > > > > >> > > > > > > > > >>>>> very good packages today, and nobody wants > > to > > > > > >> > contribute > > > > > >> > > > > > towards > > > > > >> > > > > > > > their > > > > > >> > > > > > > > > >>>>> improvement. > > > > > >> > > > > > > > > >>>>> > > > > > >> > > > > > > > > >>>>> I also think we should not copy what other > > > DBMS > > > > do > > > > > >> > since > > > > > >> > > > > their > > > > > >> > > > > > > > > >>>> ease-of-use > > > > > >> > > > > > > > > >>>>> is usually lacking (this is from someone who > > > had > > > > > to > > > > > >> > > support > > > > > >> > > > > > mysql > > > > > >> > > > > > > > and > > > > > >> > > > > > > > > >>>> pgsql > > > > > >> > > > > > > > > >>>>> deployments). > > > > > >> > > > > > > > > >>>>> > > > > > >> > > > > > > > > >>>>> Regards, > > > > > >> > > > > > > > > >>>> > > > > > >> > > > > > > > > >>> > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > -- > > > > > >> > > > > > > > > > Zhenya Stanilovsky > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > -- > > > > > >> > > > - > > > > > >> > > > Denis > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > > > > > > -- Best regards, Ivan Pavlukhin

Re: [DISCUSSION][IEP-35] Replace RunningQueryManager with GridSystemViewManager

2019-10-04 Thread Ivan Pavlukhin
; > We need metrics to build charts and history of processes. > We need system views to known what objects exist in node and its params. > > В Пт, 04/10/2019 в 11:51 +0300, Ivan Pavlukhin пишет: > > Nikolay, > > > > I checked the IEP [1]. Now it is more clear for me a

Re: Replacing default work dir from tmp to current dir

2019-10-03 Thread Ivan Pavlukhin
gt; > > > > > > I'd like everyone to pay more attention to Maven/NuGet distribution > > > > scenario. Forget about zip archive for a while. > > > > As a user, I add a dependency to Ignite package and call > > > > > > Ignition.start(). > &

Re: help on IGNITE-11894

2019-10-03 Thread Ivan Pavlukhin
org/jira/browse/IGNITE-11894 since this is my > > time > > > > working on ignite code base. I am not able to move the ticket in > > progress > > > > and would like to chat with a developer on what is expected for the > > > ticket. > > > > Is there a slack channel or message client the team uses to > > communicate? > > > > > > > > Thanks, > > > > Amit > > > > > -- Best regards, Ivan Pavlukhin

Re: [DISCUSSION][IEP-35] Replace RunningQueryManager with GridSystemViewManager

2019-10-04 Thread Ivan Pavlukhin
what is the difference between metrics and system views? > > > > > > Actually, it's a very good question :) > > > > > > System view is a collection of internal Ignite objects exported to a user. > > > Each system view is a table. > > > > > &

Re: SQL query timeout: in progress or abandoned

2019-10-14 Thread Ivan Pavlukhin
t Default Query Timeout > >>> >>> will only > >>> >>> > > > be used if user had not provided Cache Query Timeout > >>> >>> > > > > >>> >>> > > > https://github.com/apache/ignite/pull/6490/files &g

  1   2   3   4   >