Re: IGNITE-13

Valentin, I eliminated what you write me in last letter. https://github.com/javaller/MyBenchmark/commit/b3f5616f49a89d447aed26d0ac5beef5fc7aacd9 And got next results. I don't know why the test breaks down on 5-th or 6-th iteration after eliminating code from benchmark. Before: +# Benchmark: org.

new committer: Igor Sapego

I’m pleased to announce that The Project Management Committee (PMC) for Apache Ignite has invited Igor Sapego to become a committer and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submis

Re: Titles optimization for the website

Thanks Mauricio! I’ve reviewed and merged your changes. - Denis > On Mar 3, 2017, at 8:59 AM, Mauricio Stekl wrote: > > Hello Igniters, > > Based on the SEO report we sent a few weeks ago, we have optimized the > contents for titles and H1 on all pages. I have also adjusted the css a bit

Re: Additional SQL metrics

On Fri, Mar 3, 2017 at 11:07 AM, Denis Magda wrote: > What you’re saying should be default behavior. Plus, we can add a special > parameter that will gather metrics for queries executed longer that N. > Agree. I thought we already have that in some form. I remember seeing a warning for long quer

Re: Additional SQL metrics

What you’re saying should be default behavior. Plus, we can add a special parameter that will gather metrics for queries executed longer that N. — Denis > On Mar 3, 2017, at 11:01 AM, Dmitriy Setrakyan wrote: > > Hm... as a user I would be interested to know that, say, 95% of my "select > * fr

Re: Additional SQL metrics

Hm... as a user I would be interested to know that, say, 95% of my "select * from sometable where..." query executes under 10ms or so. I think holding some history is important and is not that hard to implement. D. On Fri, Mar 3, 2017 at 10:55 AM, Denis Magda wrote: > Sergey, agree, good point

Re: [VOTE] Apache Ignite 1.9.0 RC2

+1 2 мар. 2017 г. 11:45 ПП пользователь "Valentin Kulichenko" < valentin.kuliche...@gmail.com> написал: > +1 (binding) > > -Val > > On Thu, Mar 2, 2017 at 11:33 AM, Denis Magda wrote: > > > +1 (binding) > > > > — > > Denis > > > > > On Mar 2, 2017, at 9:02 AM, Anton Vinogradov > > > wrote: > >

Re: IGNITE-3422 - ready for review

Vyacheslav, sorry for the delay with a reply. Let’s put off this ticket for now because, as I see it’s too controversial for us. If no one emerges and asks that he needs it then we will close it later on. — Denis > On Mar 1, 2017, at 12:11 AM, Vyacheslav Daradur wrote: > > Guys, any thoughts?

Re: Hello Ignite Community

Hello Kartik, Welcome to the Ignite community! Please subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructi

Re: Additional SQL metrics

Sergey, agree, good point! Igniters, any other thoughts before we wrap up the discussion updating the ticket content? — Denis > On Mar 3, 2017, at 10:06 AM, Valentin Kulichenko > wrote: > > Sergey, that's great idea! Generally, user is not interested much in some > average numbers, especiall

Getting Access to Ignite's blog on ASF

Hi Cos, Could you explain how I can sign in into Ignite’s blog on ASF and edit it? https://blogs.apache.org/ignite/ — Denis

Re: Documenting Apache Ignite 1.9 Features

Guys, thanks a lot! Great work. We could achieve 100% documentation readiness for 1.9 release. Prachi, please do the language review and edit the following pages whenever is needed: 1) Review the content of blue “Streaming mode” callout at the end of this section: https://apacheignite.readme.i

Re: IGNITE-13

Hi Vadim, What do you mean by "copied benchmarks"? What changed singe previous iteration and why results are so different? As for duplicated loop, you don't need it. BinaryOutputStream allows to write a value to a particular position (even before already written data). So you can reserve 4 bytes

Re: Additional SQL metrics

Sergey, that's great idea! Generally, user is not interested much in some average numbers, especially in case of SQL queries. What they need is a list of slow queries and detailed information about the execution flow of these particular queries. -Val On Fri, Mar 3, 2017 at 2:50 AM, Sergey Kozlov

Hello Ignite Community

Hello Members, I'm new to Apache Ignite, and would like to learn, and then start contributing to Apache Ignite. If anyone wants to volunteer for guiding me or becoming my mentor through the process, I'd really appreciate that. Thanks & Regards, Kartik Somani

Titles optimization for the website

Hello Igniters, Based on the SEO report we sent a few weeks ago, we have optimized the contents for titles and H1 on all pages. I have also adjusted the css a bit so we can now use H1 on all pages instead of H2.“first", as this is much better for SEO. I am attaching a patch with all these chan

Re: REVIEW IGNITE-2552 EvictionPolicies refactored, logic changed

Aleksey, GitHub isn't official review tool in Apache Ignite community. There are two ways for code review: upsource and comments in JIRA tickets. So, I think, we should finish review of this ticket in upsource. On Thu, Mar 2, 2017 at 11:30 AM, ALEKSEY KUZNETSOV wrote: > lets review code at githu

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Maxim, I think the next implementation will be good enough: public IgniteUuid asGridUuid() { return new IgniteUuid(new UUID(nodeOrderDrId, topVer), order); } Serialization/deserialization of GridCacheVersion.globalTime field should be removed. On Fri, Mar 3, 2017 at 5:57 PM, Kozlov Maxim

[GitHub] ignite pull request #1592: Ignite 4584

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

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Alexey, public IgniteUuid asGridUuid() { return new IgniteUuid(new UUID(nodeOrderDrId << 32, topVer << 32), order); } So you want to change or not? And - GridCacheVersion.writeTo(ByteBuffer buf, MessageWriter writer) - GridCacheVersion.readFrom(ByteBuffer buf, MessageReader reader) use g

[jira] [Created] (IGNITE-4791) [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result.

Semen Boikov created IGNITE-4791: Summary: [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result. Key: IGNITE-4791 URL: https://issues.apache.org/jira/browse/IGNITE-4791 Project: Ig

[jira] [Created] (IGNITE-4790) [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result.

Semen Boikov created IGNITE-4790: Summary: [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result. Key: IGNITE-4790 URL: https://issues.apache.org/jira/browse/IGNITE-4790 Project: Ig

[jira] [Created] (IGNITE-4789) [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result.

Semen Boikov created IGNITE-4789: Summary: [IGNITE-4788] JVM crash while accessing offheap rows of SQL query result. Key: IGNITE-4789 URL: https://issues.apache.org/jira/browse/IGNITE-4789 Project: Ig

[GitHub] ignite pull request #1509: IGNITE-4624: ScanQuery shows poor performance.

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

[GitHub] ignite pull request #1425: IGNITE-4036: Near cache is not expired together w...

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

[GitHub] ignite pull request #1476: IGNITE-4106: SQL: parallelize sql queries over ca...

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

[jira] [Created] (IGNITE-4788) JVM crash while accessing offheap rows of SQL query result.

Andrew Mashenkov created IGNITE-4788: Summary: JVM crash while accessing offheap rows of SQL query result. Key: IGNITE-4788 URL: https://issues.apache.org/jira/browse/IGNITE-4788 Project: Ignite

[GitHub] ignite pull request #1591: Ignite 4558

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

[jira] [Created] (IGNITE-4787) Performance drop sql-merge-all 1.9 vs 1.8

Ilya Suntsov created IGNITE-4787: Summary: Performance drop sql-merge-all 1.9 vs 1.8 Key: IGNITE-4787 URL: https://issues.apache.org/jira/browse/IGNITE-4787 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-4786) Try get rid of exchange futures and affinity history

Semen Boikov created IGNITE-4786: Summary: Try get rid of exchange futures and affinity history Key: IGNITE-4786 URL: https://issues.apache.org/jira/browse/IGNITE-4786 Project: Ignite Issue T

[jira] [Created] (IGNITE-4785) Web Console: Implement floating menu with base buttons

Vica Abramova created IGNITE-4785: - Summary: Web Console: Implement floating menu with base buttons Key: IGNITE-4785 URL: https://issues.apache.org/jira/browse/IGNITE-4785 Project: Ignite Is

[jira] [Created] (IGNITE-4784) Web Console: Revise demo mode

Vica Abramova created IGNITE-4784: - Summary: Web Console: Revise demo mode Key: IGNITE-4784 URL: https://issues.apache.org/jira/browse/IGNITE-4784 Project: Ignite Issue Type: Task C

[jira] [Created] (IGNITE-4783) Web Console: Revise 'become a user' mechanics

Vica Abramova created IGNITE-4783: - Summary: Web Console: Revise 'become a user' mechanics Key: IGNITE-4783 URL: https://issues.apache.org/jira/browse/IGNITE-4783 Project: Ignite Issue Type:

Re: general question

Yes, DHT stands for distributed hash table. On Fri, Mar 3, 2017 at 3:01 PM, ALEKSEY KUZNETSOV wrote: > Thank you so much! And the last one. I cannot find definition of DHT. Does > it stand for distributed ? In contrary to Local > > пт, 3 мар. 2017 г. в 13:51, Alexander Fedotov < > alexander.fedo

[jira] [Created] (IGNITE-4782) Web Console: Revise on-boarding behavior and user's education

Vica Abramova created IGNITE-4782: - Summary: Web Console: Revise on-boarding behavior and user's education Key: IGNITE-4782 URL: https://issues.apache.org/jira/browse/IGNITE-4782 Project: Ignite

Re: general question

Thank you so much! And the last one. I cannot find definition of DHT. Does it stand for distributed ? In contrary to Local пт, 3 мар. 2017 г. в 13:51, Alexander Fedotov : > Probably, IgniteTxHandler#processDhtTxPrepareRequest is what you are > looking for. > Check the data flow from GridDhtTxPrep

[jira] [Created] (IGNITE-4781) Web Console: Revise the Queries Screen

Vica Abramova created IGNITE-4781: - Summary: Web Console: Revise the Queries Screen Key: IGNITE-4781 URL: https://issues.apache.org/jira/browse/IGNITE-4781 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-4780) Web Console: Improve the adaptability of the web console

Vica Abramova created IGNITE-4780: - Summary: Web Console: Improve the adaptability of the web console Key: IGNITE-4780 URL: https://issues.apache.org/jira/browse/IGNITE-4780 Project: Ignite I

[jira] [Created] (IGNITE-4779) Missed discovery data snapshot during exchange processing

Semen Boikov created IGNITE-4779: Summary: Missed discovery data snapshot during exchange processing Key: IGNITE-4779 URL: https://issues.apache.org/jira/browse/IGNITE-4779 Project: Ignite Is

[jira] [Created] (IGNITE-4778) [IGNITE-4777] Web Console: Add notification on 'Download project' button

Semen Boikov created IGNITE-4778: Summary: [IGNITE-4777] Web Console: Add notification on 'Download project' button Key: IGNITE-4778 URL: https://issues.apache.org/jira/browse/IGNITE-4778 Project: Ign

[jira] [Created] (IGNITE-4777) Web Console: Add notification on 'Download project' button

Vica Abramova created IGNITE-4777: - Summary: Web Console: Add notification on 'Download project' button Key: IGNITE-4777 URL: https://issues.apache.org/jira/browse/IGNITE-4777 Project: Ignite

Re: code refactoring suggestion

Aleksey, once again, listener will be called directly in GridFutureAdapter.listen() method if future already completed. 1. execute prepareAsync() 2. prepare phase answer got 3. listener binded (actually not binded but called) @Override public void listen(IgniteInClosure> lsnr0) { assert lsnr

Re: general question

Probably, IgniteTxHandler#processDhtTxPrepareRequest is what you are looking for. Check the data flow from GridDhtTxPrepareRequest#nearWrites On Fri, Mar 3, 2017 at 1:19 PM, ALEKSEY KUZNETSOV wrote: > Ah, thanks! Which class is responsible for near cache synchronization ? > > пт, 3 мар. 2017 г.

Re: Additional SQL metrics

One more comment: In general the customer is interested in slow queries details thus we can introduce an option which will allow to store only queries executed more than NNN seconds. It may significantly reduce the the memory consumption for history (but logging of all queries is still available i

Re: IgniteConfiguration.gridName is very confusing

Hi, it's ready for review http://reviews.ignite.apache.org/ignite/review/IGNT-CR-81 On Fri, Mar 3, 2017 at 11:39 AM, Yakov Zhdanov wrote: > Guys, I want to bring this up. What is the status of this ticket and > further steps? > > --Yakov > > 2017-01-30 16:37 GMT+03:00 Alexander Fedotov >: > > >

Re: general question

Ah, thanks! Which class is responsible for near cache synchronization ? пт, 3 мар. 2017 г. в 13:15, Alexander Fedotov : > Hi Aleksey, > > Local cache pertains only to the node where it's created and no data is > distributed to > or synchronized with other nodes, while near cache serves as a front

[GitHub] ignite pull request #1590: ignite-4680

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

[jira] [Created] (IGNITE-4776) DDL: handle client disconnec

Vladimir Ozerov created IGNITE-4776: --- Summary: DDL: handle client disconnec Key: IGNITE-4776 URL: https://issues.apache.org/jira/browse/IGNITE-4776 Project: Ignite Issue Type: Sub-task

Re: general question

Hi Aleksey, Local cache pertains only to the node where it's created and no data is distributed to or synchronized with other nodes, while near cache serves as a front end for a partitioned cache, storing recently requested data which is synchronized when it's changed on other nodes. On Fri, Mar

[jira] [Created] (IGNITE-4775) Web Console: Implement role-based access control

Vica Abramova created IGNITE-4775: - Summary: Web Console: Implement role-based access control Key: IGNITE-4775 URL: https://issues.apache.org/jira/browse/IGNITE-4775 Project: Ignite Issue Typ

[jira] [Created] (IGNITE-4774) Web Console: Improve design of tables

Vica Abramova created IGNITE-4774: - Summary: Web Console: Improve design of tables Key: IGNITE-4774 URL: https://issues.apache.org/jira/browse/IGNITE-4774 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-4773) Web Console: Create New Design Concept

Vica Abramova created IGNITE-4773: - Summary: Web Console: Create New Design Concept Key: IGNITE-4773 URL: https://issues.apache.org/jira/browse/IGNITE-4773 Project: Ignite Issue Type: Improve

Re: Documenting Apache Ignite 1.9 Features

I've written new sections about streaming both on that hidden jdbc 1.9 page and in (hidden for now and created by myself) DML 1.9 page - figured that it might be a good thing to give the user a hint about having a way to stream data via SQL on DML page as they could probably miss it if we don't men

Re: IGNITE-13

Valentin, What do you think about duplicated cycle in strToBinaryOutputStream ? How to calculate StrLen для outBinaryHeap without this cycle ? public class BinaryUtilsNew extends BinaryUtils { public static int getStrLen(String val) { int strLen = val.length(); int utfLen =

Re: IgniteConfiguration.gridName is very confusing

Guys, I want to bring this up. What is the status of this ticket and further steps? --Yakov 2017-01-30 16:37 GMT+03:00 Alexander Fedotov : > Done. But it looks like something went wrong since Upsource reports: > "Review has too many files (1244), aborting". > > Also guys, I believe we need to me

Re: PR IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception occurs during cache initialization

Alexey, my comments are in the ticket. Please address them. Thanks! -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com 2017-03-01 12:15 GMT+03:00 Yakov Zhdanov : > Alexey, I will take a look at this in couple of days. > > --Yakov > > 2017-03-01 11:25 GMT+03:00 ALEKSEY KUZNETSOV :

Re: IGNITE-13

Hello Colleagues! I've just copied benchmarks and gotten interest results. https://github.com/javaller/MyBenchmark/blob/master/03_03_17_out.txt Time increase in 5, 6 Iteration in both cases. What do you think about it? Vadim 2017-03-03 2:00 GMT+03:00 Valentin Kulichenko : > Vadim, > > Looks

Re: IGNITE-603

Thanks, Alex! I will take a look in a couple of days Thanks! -- Yakov Zhdanov, Director R&D *GridGain Systems* www.gridgain.com 2017-03-02 19:07 GMT+03:00 Александр Меньшиков : > Yakov, Okay. You can see result in JIRA https://issues.apache.org/ > jira/browse/IGNITE-603 > > 2017-02-28 19:31 GMT+