Re: [DISCUSSION] Ignite integration testing framework.

;with Ignite under test. We use py4j Python-Java gateway library > > to > > >>>>>&

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

t; > > > 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. > > > > Vyacheslav, thanks for supporting the community and keep the pace! &

[jira] [Created] (IGNITE-12233) Merge benchmarks sql index benchmarks from ignite-2.7 to master

Ilya Suntsov created IGNITE-12233: - Summary: Merge benchmarks sql index benchmarks from ignite-2.7 to master Key: IGNITE-12233 URL: https://issues.apache.org/jira/browse/IGNITE-12233 Project: Ignite

[jira] [Created] (IGNITE-11319) ignitevisorcmd can't handle incorrect !q parameter

Ilya Suntsov created IGNITE-11319: - Summary: ignitevisorcmd can't handle incorrect !q parameter Key: IGNITE-11319 URL: https://issues.apache.org/jira/browse/IGNITE-11319 Project: Ignite

[jira] [Created] (IGNITE-11306) NativeSqlJoinQueryRangeBenchmark doesn't work

Ilya Suntsov created IGNITE-11306: - Summary: NativeSqlJoinQueryRangeBenchmark doesn't work Key: IGNITE-11306 URL: https://issues.apache.org/jira/browse/IGNITE-11306 Project: Ignite Issue

[jira] [Created] (IGNITE-11307) SqlNative benchmarks failed with more than 1 client

Ilya Suntsov created IGNITE-11307: - Summary: SqlNative benchmarks failed with more than 1 client Key: IGNITE-11307 URL: https://issues.apache.org/jira/browse/IGNITE-11307 Project: Ignite

[jira] [Created] (IGNITE-10918) Implement C++, .Net thin benchmarks

Ilya Suntsov created IGNITE-10918: - Summary: Implement C++, .Net thin benchmarks Key: IGNITE-10918 URL: https://issues.apache.org/jira/browse/IGNITE-10918 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-10842) Exception during node stopping

Ilya Suntsov created IGNITE-10842: - Summary: Exception during node stopping Key: IGNITE-10842 URL: https://issues.apache.org/jira/browse/IGNITE-10842 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-10800) Add wal_mode parameter to properties file

Ilya Suntsov created IGNITE-10800: - Summary: Add wal_mode parameter to properties file Key: IGNITE-10800 URL: https://issues.apache.org/jira/browse/IGNITE-10800 Project: Ignite Issue Type

[jira] [Created] (IGNITE-10170) .NET: Services.ServicesTestAsync fails

Ilya Suntsov created IGNITE-10170: - Summary: .NET: Services.ServicesTestAsync fails Key: IGNITE-10170 URL: https://issues.apache.org/jira/browse/IGNITE-10170 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-10148) Add aws s3 and elb configs to benchmarks/config

Ilya Suntsov created IGNITE-10148: - Summary: Add aws s3 and elb configs to benchmarks/config Key: IGNITE-10148 URL: https://issues.apache.org/jira/browse/IGNITE-10148 Project: Ignite Issue

[jira] [Created] (IGNITE-9534) Wrong error message in bin/include/functions.sh

Ilya Suntsov created IGNITE-9534: Summary: Wrong error message in bin/include/functions.sh Key: IGNITE-9534 URL: https://issues.apache.org/jira/browse/IGNITE-9534 Project: Ignite Issue Type

Re: New PMC member: Dmitriy Pavlov

Dmitriy, congrats! It is really great news! On Fri, Aug 31, 2018, 02:30 Saikat Maitra wrote: > Dmitriy, > > Congratulations !!! > > My best wishes :) > > Regards, > Saikat > > > > On Thu, Aug 30, 2018 at 1:20 PM, Pavel Kovalenko > wrote: > > > Dmitriy, > > > > Congratulations. This is very

[jira] [Created] (IGNITE-9417) IgniteSqlInsertIndexedValueBenchamrks failed with more than one driver

Ilya Suntsov created IGNITE-9417: Summary: IgniteSqlInsertIndexedValueBenchamrks failed with more than one driver Key: IGNITE-9417 URL: https://issues.apache.org/jira/browse/IGNITE-9417 Project

Re: Benchmarking

; a branches comparision. > > > > > > So, my question is: > > > Is there anybody at community able to perform benchmarks on real > hardware > > > and already have automation to compare 2 branches? > > > > > > > -- > Best Regards, Vyacheslav D. > -- Best Regards, Ilya Suntsov email: isunt...@gridgain.com *GridGain Systems* www.gridgain.com

Re: [BENCHMARK REQUEST] IGNITE-8446

can be completed in second (please > use same as you use to check the release) > - in-memory > - default > - same you use at pre-release check. > > пт, 3 авг. 2018 г. в 15:38, Ilya Suntsov : > >> Anton, >> >> Please provide more details: >> >>- B

Re: [BENCHMARK REQUEST] IGNITE-8446

you please check https://issues.apache.org/jira/browse/IGNITE-8446? >> >> We have to check >> https://github.com/apache/ignite/tree/ignite-8446 >> vs >> https://github.com/apache/ignite/tree/ignite-8446-master >> >> Only one benchmark is required: tx throughput >> > -- Best Regards, Ilya Suntsov email: isunt...@gridgain.com *GridGain Systems* www.gridgain.com

Re: iep-6 metrics ticket review

mail.com >> > > > wrote: >> > > >> > > > Hi ,Igniters! >> > > > >> > > > Do we still need this ticket, about invoke metrics : [1] ? >> > > > >> > > > If yes, than could somebody review it ? >> > > > >> > > > If no, should we close this ticket ? >> > > > >> > > > [1] : https://issues.apache.org/jira/browse/IGNITE-6846 >> > > > -- >> > > > >> > > > *Best Regards,* >> > > > >> > > > *Kuznetsov Aleksey* >> > > > >> > > >> > >> > -- Best Regards, Ilya Suntsov email: isunt...@gridgain.com *GridGain Systems* www.gridgain.com

Re: [VOTE] Apache Ignite 2.6.0 RC1

lease confirm that all changes [1] expected > [1] > https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_ > IgniteRelease72CheckFileConsistency/1478134:id/results/result.log > > ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov : > > > Anton, > >

Re: [VOTE] Apache Ignite 2.6.0 RC1

HistoryList_ApacheIgniteReleaseJava8=__all_branches__ > > >> [2] > > >> > > >> > > https://ci.ignite.apache.org/viewType.html?buildTypeId= > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum= > buildTypeHistoryList_ApacheIgniteReleaseJava8=__all_branches__ > > >> > > >> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov >: > > >> > > >> > +1 (binding) > > >> > > > >> > Download sources: OK > > >> > Build from sources: OK > > >> > Run ignite.bat: OK > > >> > > > >> > -- > > >> > Alexey Kuznetsov > > >> > > > >> > > > > > > > > > -- Best Regards, Ilya Suntsov email: isunt...@gridgain.com *GridGain Systems* www.gridgain.com

Re: [VOTE] Apache Ignite 2.6.0 RC1

>> https://issues.apache.org/jira/issues/?jql=project%20% > > 3D%20IGNITE%20AND% > > >> > 20fixVersion%20%3D%202.6%20AND%20(status%20%3D% > > >> > 20closed%20or%20status%20%3D%20resolved) > > >> > > > >> > DEVNOTES > > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_ > > >> > plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1 > > >> > > > >> > RELEASE NOTES > > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_ > > >> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1 > > >> > > > >> > Please start voting. > > >> > > > >> > +1 - to accept Apache Ignite 2.6.0-RC1 > > >> > 0 - don't care either way > > >> > -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why) > > >> > > > >> > This vote will go for 72 hours. > > >> > > > >> > > > > > > -- Best Regards, Ilya Suntsov email: isunt...@gridgain.com *GridGain Systems* www.gridgain.com

[jira] [Created] (IGNITE-8864) sql-query-put x 5 performance drop

Ilya Suntsov created IGNITE-8864: Summary: sql-query-put x 5 performance drop Key: IGNITE-8864 URL: https://issues.apache.org/jira/browse/IGNITE-8864 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-8733) Add benchmarks for NodeJS thin client

Ilya Suntsov created IGNITE-8733: Summary: Add benchmarks for NodeJS thin client Key: IGNITE-8733 URL: https://issues.apache.org/jira/browse/IGNITE-8733 Project: Ignite Issue Type

Apache ignite client for YCSB

Hi Brian, I would like to add Apache Ignite (https://apacheignite.readme.io/docs) client to YCSB repository. Pull request passed all travis tests: https://github.com/brianfrankcooper/YCSB/pull/1118 Could you please take a look at this PR? -- Best Regards, Ilya Suntsov email: isunt

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

p and which commit caused it? It should not be affected by changes > in > > > persistence at all. > > > > > > D. > > > > > > On Tue, Apr 10, 2018 at 7:56 AM, Ilya Suntsov <isunt...@gridgain.com> > > > wrote: > > > > > > > Ign

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

t;> does not make much sense. > > >>>>>>>>>>>>>>>>>> What Ivan mentioned here as drop, in relation to old > > mode > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> DEFAULT > > >>>>>>>>>>>>>>>> (FSYNC > > >>>>>>>>>>> now), is still significant perfromance boost. > > >>>>>>>>>>>>>>>>> Sincerely, > > >>>>>>>>>>>>>>>>>> Dmitriy Pavlov > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> ср, 21 мар. 2018 г. в 17:56, Ivan Rakov < > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> ivan.glu...@gmail.com > > >>>>>>>>>>>>>>>> : > > >>>>>>>>>> I've attached benchmark results to the JIRA ticket. > > >>>>>>>>>>>> We observe ~7% drop in "fair" LOG_ONLY_SAFE mode, > > >>>>>>>>>>>>>>>>>>> independent > > >>>>>>>>>>>>>>>>> of > > >>>>>>>>> WAL > > >>>>>>>>>>> compaction enabled flag. It's pretty significant drop: WAL > > >>>>>>>>>>>>>>>>> compaction > > >>>>>>>>>>>>>>>>> itself gives only ~3% drop. > > >>>>>>>>>>>>>>>>> I see two options here: > > >>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> 1) Change LOG_ONLY behavior. That implies that we'll > be > > >>>>>>>>>>>>>>>>>>> ready > > >>>>>>>>>>>>>>>>> to > > >>>>>>>>> release > > >>>>>>>>>>> AI 2.5 with 7% drop. > > >>>>>>>>>>>>>>>>>> 2) Introduce LOG_ONLY_SAFE, make it default, add > release > > >>>>>>>>>>>>>>>>>>> note > > >>>>>>>>>>>>>>>>> to AI > > >>>>>>>>> 2.5 > > >>>>>>>>>>>>>>>>>> that we added power loss durability in default mode, > but > > >>>>>>>>>>>>>>>>> user > > >>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>> may > > >>>>>>>>>>>>>>> fallback to previous LOG_ONLY in order to retain > > >>>>>>>>>> performance. > > >>>>>>>>>>>>>>>>> Thoughts? > > >>>>>>>>> Best Regards, > > >>>>>>>>>>>>>>>>>>> Ivan Rakov > > >>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>> On 20.03.2018 16:00, Ivan Rakov wrote: > > >>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>> Val, > > >>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>> If a storage is in > > >>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>> corrupted state, does it mean that it needs to be > > >>>>>>>>>>>>>>>>>>>>> completely > > >>>>>>>>>>>>>>>>>>> removed > > >>>>>>>>>> and > > >>>>>>>>>>>>>>>>>> cluster needs to be restarted without data? > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>> Yes, there's a chance that in LOG_ONLY all local data > > >> will > > >>>>>>>>>>>>>>>>>>>> be > > >>>>>>>>>>>>>>>>>> lost, > > >>>>>>>>>> but only in *power loss**/ OS crash* case. > > >>>>>>>>>>>>>>>>> kill -9, JVM crash, death of critical system thread and > > >>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> all > > >>>>>>>>>>>>>>>>>> other > > >>>>>>>>> cases that usually take place are variations of *process > > >>>>>>>>>>>>>>>>>>>> crash*. > > >>>>>>>>>>>>>>>>>> All > > >>>>>>>>>>> WAL modes (except NONE, of course) ensure corruption-safety > > >>>>>>>>>>>>>>>>> in > > >>>>>>>>>>>>>>> case > > >>>>>>>>> of > > >>>>>>>>>>>>>>>>> process crash. > > >>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> If so, I'm not sure any mode > > >>>>>>>>>>>>>>>>>>>> that allows corruption makes much sense to me. > > >>>>>>>>>>>>>>>>>>>>> It depends on performance impact of enforcing > > >> power-loss > > >>>>>>>>>>>>>>>>>>>> corruption > > >>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>> safety. Price of full protection from power loss is > > high > > >> - > > >>>>>>>>>>>>>>>>> FSYNC > > >>>>>>>>>>>>>> is > > >>>>>>>>> way slower (2-10 times) than other WAL modes. The question is > > >>>>>>>>>>>>>>>>> whether > > >>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> ensuring weaker guarantees (corruption can't happen, > but > > >>>>>>>>>>>>>>>>>> loss > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>> of > > >>>>>>>>>>>>>>> last > > >>>>>>>>>> updates can) will affect performance as badly as strong > > >>>>>>>>>>>>>>>>>> guarantees. > > >>>>>>>>>>>>>>>>>> I'll share benchmark results soon. > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>> Best Regards, > > >>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> Ivan Rakov > > >>>>>>>>>>>>>>>>>>>> On 20.03.2018 5:09, Valentin Kulichenko wrote: > > >>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>> Guys, > > >>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>> What do we understand under "data corruption" here? > > If > > >> a > > >>>>>>>>>>>>>>>>>>>>> storage > > >>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>> is > > >>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>> in > > >>>>>>>>>>>>>>>>>> corrupted state, does it mean that it needs to be > > >> completely > > >>>>>>>>>>>>>>>>>> removed > > >>>>>>>>>>>>>>>>>>> and > > >>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> cluster needs to be restarted without data? If so, I'm > > not > > >>>>>>>>>>>>>>>>>> sure > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>> any > > >>>>>>>>>> mode > > >>>>>>>>>>>>>>>>>> that allows corruption makes much sense to me. How am > I > > >>>>>>>>>>>>>>>>>> supposed > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>> to > > >>>>>>>>>>> use a > > >>>>>>>>>>>>>>>>>> database, if virtually any failure can end with > complete > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>> loss of > > >>>>>>>>>>>>>>>>>>>>> data? > > >>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>> In any case, this definitely should not be a default > > >>>>>>>>>>>>>>>>>> behavior. > > >>>>>>>>>>>>>>>> If > > >>>>>>>>> user ever > > >>>>>>>>>>>>>>>>>> switches to corruption-unsafe mode, there should be a > > >>>>>>>>>>>>>>>>>> clear > > >>>>>>>>>>>>>>>>>>> warning > > >>>>>>>>> about > > >>>>>>>>>>>>>>>>>> this. > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>> -Val > > >>>>>>>>>>>>>>>>>>>>> On Fri, Mar 16, 2018 at 1:06 AM, Ivan Rakov < > > >>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>> ivan.glu...@gmail.com> > > >>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>> wrote: > > >>>>>>>>>>>>>>>>>> Ticket to track changes: > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-7754 > > >>>>>>>>>>>>>>>>>>>>>> Best Regards, > > >>>>>>>>>>>>>>>>>>>>>> Ivan Rakov > > >>>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>>> On 16.03.2018 10:58, Dmitriy Setrakyan wrote: > > >>>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>>> On Fri, Mar 16, 2018 at 12:55 AM, Ivan Rakov < > > >>>>>>>>>>>>>>>>>>>>>> ivan.glu...@gmail.com > > >>>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>>> wrote: > > >>>>>>>>>>>>>>>>>>>> Vladimir, > > >>>>>>>>>>>>>>>>>>>> Unlike BACKGROUND, LOG_ONLY provides strict write > > >>>>>>>>>>>>>>>>>>>>>>> guarantees > > >>>>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>>> unless power > > >>>>>>>>>>> loss has happened. > > >>>>>>>>>>>>>>>>>>>>>>>> Seems like we need to measure performance > > difference > > >>>>>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>>>>> to > > >>>>>>>>>>>>>>>>>>>>>> decide > > >>>>>>>>> whether do > > >>>>>>>>>>>>>>>>>>>>> we need separate WAL mode. If it will be invisible, > > >>>>>>>>>>>>>>>>>> we'll > > >>>>>>>>>>>>>>>>>>>>>> just > > >>>>>>>>>> fix > > >>>>>>>>>>>>>>>>>>>>> these > > >>>>>>>>>>>>>>>>>> bugs without introducing new mode; if it will be > > >>>>>>>>>>>>>>>>>>>> perceptible, > > >>>>>>>>>>>>>>>>>>>>>>>> we'll > > >>>>>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>>>> continue the discussion about introducing > > >>>>>>>>>>>>>>>>>>>>>> LOG_ONLY_SAFE. > > >>>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>> Makes sense? > > >>>>>>>>>>>>>>>>>>>> Yes, this sounds like the right approach. > > >>>>>>>>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>>>>>>>> > > > > > -- Best Regards, Ilya Suntsov email: isunt...@gridgain.com *GridGain Systems* www.gridgain.com

[jira] [Created] (IGNITE-7768) No description for org.apache.ignite.ml.nn.trainers.distributed

Ilya Suntsov created IGNITE-7768: Summary: No description for org.apache.ignite.ml.nn.trainers.distributed Key: IGNITE-7768 URL: https://issues.apache.org/jira/browse/IGNITE-7768 Project: Ignite

[jira] [Created] (IGNITE-7410) IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs

Ilya Suntsov created IGNITE-7410: Summary: IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs Key: IGNITE-7410 URL: https://issues.apache.org/jira/browse/IGNITE-7410 Project: Ignite

[jira] [Created] (IGNITE-7245) Missing description in javadoc for ignite-dev-utils

Ilya Suntsov created IGNITE-7245: Summary: Missing description in javadoc for ignite-dev-utils Key: IGNITE-7245 URL: https://issues.apache.org/jira/browse/IGNITE-7245 Project: Ignite Issue

[jira] [Created] (IGNITE-7244) Missing README.txt for ignite-dev-utils module

Ilya Suntsov created IGNITE-7244: Summary: Missing README.txt for ignite-dev-utils module Key: IGNITE-7244 URL: https://issues.apache.org/jira/browse/IGNITE-7244 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7241) Create shell (bat) script for run IgniteWalConverter

Ilya Suntsov created IGNITE-7241: Summary: Create shell (bat) script for run IgniteWalConverter Key: IGNITE-7241 URL: https://issues.apache.org/jira/browse/IGNITE-7241 Project: Ignite Issue

[jira] [Created] (IGNITE-7240) Upload ignite-dev-utils module in maven

Ilya Suntsov created IGNITE-7240: Summary: Upload ignite-dev-utils module in maven Key: IGNITE-7240 URL: https://issues.apache.org/jira/browse/IGNITE-7240 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-7212) Load stoped after server node kill

Ilya Suntsov created IGNITE-7212: Summary: Load stoped after server node kill Key: IGNITE-7212 URL: https://issues.apache.org/jira/browse/IGNITE-7212 Project: Ignite Issue Type: Bug

Re: Adding sqlline tool to Apache Ignite project

2017-08-25 18:48 GMT+03:00 Denis Magda <dma...@apache.org>: > >>> > >>>> Hi Ilya, > >>>> > >>>> It will be a useful addition to Ignite. I would include the tool in > one of > >>>> the nearest relea

Re: Adding sqlline tool to Apache Ignite project

2017-08-25 18:48 GMT+03:00 Denis Magda <dma...@apache.org>: > >>> > >>>> Hi Ilya, > >>>> > >>>> It will be a useful addition to Ignite. I would include the tool in > one of > >>>> the nearest relea

[jira] [Created] (IGNITE-6561) Include sqlline in Apache Ignite

Ilya Suntsov created IGNITE-6561: Summary: Include sqlline in Apache Ignite Key: IGNITE-6561 URL: https://issues.apache.org/jira/browse/IGNITE-6561 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6478) IndexOutOfBoundsException jdbc2

Ilya Suntsov created IGNITE-6478: Summary: IndexOutOfBoundsException jdbc2 Key: IGNITE-6478 URL: https://issues.apache.org/jira/browse/IGNITE-6478 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6479) IndexOutOfBoundsException jdbc2

Ilya Suntsov created IGNITE-6479: Summary: IndexOutOfBoundsException jdbc2 Key: IGNITE-6479 URL: https://issues.apache.org/jira/browse/IGNITE-6479 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6457) Incorrect exception when used schema name in lower case

Ilya Suntsov created IGNITE-6457: Summary: Incorrect exception when used schema name in lower case Key: IGNITE-6457 URL: https://issues.apache.org/jira/browse/IGNITE-6457 Project: Ignite

[jira] [Created] (IGNITE-6448) Select * doesn't return new field name after concurrent ALTER TABLE

Ilya Suntsov created IGNITE-6448: Summary: Select * doesn't return new field name after concurrent ALTER TABLE Key: IGNITE-6448 URL: https://issues.apache.org/jira/browse/IGNITE-6448 Project: Ignite

Re: [VOTE] Apache Ignite 2.2.0 RC2

.txt;hb=refs/tags/2.2.0-rc2 > > > > Please start voting. > > > > +1 - to accept Apache Ignite 2.2.0-RC2 > > 0 - don't care either way > > -1 - DO NOT accept Apache Ignite 2.2.0-RC2 (explain why) > > > > This vote will go for 72 hours. > > > -- Ilya Suntsov

[jira] [Created] (IGNITE-6315) Exception during DistributedRegressionExample (ML)

Ilya Suntsov created IGNITE-6315: Summary: Exception during DistributedRegressionExample (ML) Key: IGNITE-6315 URL: https://issues.apache.org/jira/browse/IGNITE-6315 Project: Ignite Issue

Re: New API docs look for Ignite.NET

t/dotnetdoc/index.html > [3] https://dotnet.github.io/docfx/ > [4] https://issues.apache.org/jira/browse/IGNITE-6253 > [5] https://ptupitsyn.github.io/docfx-test/api/index.html > -- Ilya Suntsov

[jira] [Created] (IGNITE-6226) Review docs for integration with Apache Zeppelin

Ilya Suntsov created IGNITE-6226: Summary: Review docs for integration with Apache Zeppelin Key: IGNITE-6226 URL: https://issues.apache.org/jira/browse/IGNITE-6226 Project: Ignite Issue Type

Adding sqlline tool to Apache Ignite project

+sqlline+tool The most problems with sqlline relate with some issues from our side or some unsupported features. Would be nice to add tool like this (sqlline or something else) in our project. Have you any objections or other thoughts? -- Ilya Suntsov

[jira] [Created] (IGNITE-6177) Update docs for integration with Apache Zeppelin

Ilya Suntsov created IGNITE-6177: Summary: Update docs for integration with Apache Zeppelin Key: IGNITE-6177 URL: https://issues.apache.org/jira/browse/IGNITE-6177 Project: Ignite Issue Type

[jira] [Created] (IGNITE-6152) Wrong response from grid via jdbc driver

Ilya Suntsov created IGNITE-6152: Summary: Wrong response from grid via jdbc driver Key: IGNITE-6152 URL: https://issues.apache.org/jira/browse/IGNITE-6152 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-6126) Compilation error (yardstick repo)

Ilya Suntsov created IGNITE-6126: Summary: Compilation error (yardstick repo) Key: IGNITE-6126 URL: https://issues.apache.org/jira/browse/IGNITE-6126 Project: Ignite Issue Type: Bug

Re: [VOTE] Apache Ignite 2.1.0 RC1

Lgpl binaries should not to be in svn. This build will be removed. 15 июля 2017 г. 1:52 PM пользователь "Sergey Kozlov" написал: > Igniters > > Could someone explain why we include LGPL binary fabric [1] in the release? > Either it was a mistake or we should upload also

[jira] [Created] (IGNITE-5735) NPE during populated data (CacheQueryDdlExample)

Ilya Suntsov created IGNITE-5735: Summary: NPE during populated data (CacheQueryDdlExample) Key: IGNITE-5735 URL: https://issues.apache.org/jira/browse/IGNITE-5735 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5538) NPE (PersistentStoreExample)

Ilya Suntsov created IGNITE-5538: Summary: NPE (PersistentStoreExample) Key: IGNITE-5538 URL: https://issues.apache.org/jira/browse/IGNITE-5538 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5537) bin/control.sh add validation of input parameters

Ilya Suntsov created IGNITE-5537: Summary: bin/control.sh add validation of input parameters Key: IGNITE-5537 URL: https://issues.apache.org/jira/browse/IGNITE-5537 Project: Ignite Issue

[jira] [Created] (IGNITE-5098) Missed ignite-rocketmq/licenses/ignite-2.0.txt

Ilya Suntsov created IGNITE-5098: Summary: Missed ignite-rocketmq/licenses/ignite-2.0.txt Key: IGNITE-5098 URL: https://issues.apache.org/jira/browse/IGNITE-5098 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5096) Too many files with unapproved license

Ilya Suntsov created IGNITE-5096: Summary: Too many files with unapproved license Key: IGNITE-5096 URL: https://issues.apache.org/jira/browse/IGNITE-5096 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-5022) Duplicates of JVM OPTS [yardstick]

Ilya Suntsov created IGNITE-5022: Summary: Duplicates of JVM OPTS [yardstick] Key: IGNITE-5022 URL: https://issues.apache.org/jira/browse/IGNITE-5022 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-4913) Update yardstick properties files

Ilya Suntsov created IGNITE-4913: Summary: Update yardstick properties files Key: IGNITE-4913 URL: https://issues.apache.org/jira/browse/IGNITE-4913 Project: Ignite Issue Type: Improvement

[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-4743) Set AUTO_COPY to false when it wasn't define in properties file

Ilya Suntsov created IGNITE-4743: Summary: Set AUTO_COPY to false when it wasn't define in properties file Key: IGNITE-4743 URL: https://issues.apache.org/jira/browse/IGNITE-4743 Project: Ignite

[jira] [Created] (IGNITE-4512) Doesnt work sql-delete benchmark

Ilya Suntsov created IGNITE-4512: Summary: Doesnt work sql-delete benchmark Key: IGNITE-4512 URL: https://issues.apache.org/jira/browse/IGNITE-4512 Project: Ignite Issue Type: Bug

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

re useful. Ilya Suntsov, basing on > your experience, please suggest which configs makes sense to include into > every Ignite release. > > Oleg, also please note that community decided to include not only the > benchmarking binaries but the sources as well into every Apache Ignit

[jira] [Created] (IGNITE-4373) Performance drop tx-putAll 1.8.0 vs 1.7.0

Ilya Suntsov created IGNITE-4373: Summary: Performance drop tx-putAll 1.8.0 vs 1.7.0 Key: IGNITE-4373 URL: https://issues.apache.org/jira/browse/IGNITE-4373 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-4282) Javadoc broken

Ilya Suntsov created IGNITE-4282: Summary: Javadoc broken Key: IGNITE-4282 URL: https://issues.apache.org/jira/browse/IGNITE-4282 Project: Ignite Issue Type: Bug Components

[jira] [Created] (IGNITE-3814) Unstable results of compute benchmarks

Ilya Suntsov created IGNITE-3814: Summary: Unstable results of compute benchmarks Key: IGNITE-3814 URL: https://issues.apache.org/jira/browse/IGNITE-3814 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-3387) NPE deploy ignite with mesos

Ilya Suntsov created IGNITE-3387: Summary: NPE deploy ignite with mesos Key: IGNITE-3387 URL: https://issues.apache.org/jira/browse/IGNITE-3387 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

Ilya Suntsov created IGNITE-3176: Summary: Need to create gc log for each client separately [ yardstick-ignite ] Key: IGNITE-3176 URL: https://issues.apache.org/jira/browse/IGNITE-3176 Project

[jira] [Created] (IGNITE-3106) Yardstick can't parse /config/queries.txt with license header

Ilya Suntsov created IGNITE-3106: Summary: Yardstick can't parse /config/queries.txt with license header Key: IGNITE-3106 URL: https://issues.apache.org/jira/browse/IGNITE-3106 Project: Ignite

[jira] [Created] (IGNITE-3103) No description in javadoc (kafka module)

Ilya Suntsov created IGNITE-3103: Summary: No description in javadoc (kafka module) Key: IGNITE-3103 URL: https://issues.apache.org/jira/browse/IGNITE-3103 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-3070) Failed to fetch data from node at org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor

Ilya Suntsov created IGNITE-3070: Summary: Failed to fetch data from node at org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor Key: IGNITE-3070 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-2932) IgniteFutureTimeoutException during the run of load test (cache-tx-invoke)

Ilya Suntsov created IGNITE-2932: Summary: IgniteFutureTimeoutException during the run of load test (cache-tx-invoke) Key: IGNITE-2932 URL: https://issues.apache.org/jira/browse/IGNITE-2932 Project

[jira] [Created] (IGNITE-2896) IgniteFutureTimeoutException during load test (yardstick)

Ilya Suntsov created IGNITE-2896: Summary: IgniteFutureTimeoutException during load test (yardstick) Key: IGNITE-2896 URL: https://issues.apache.org/jira/browse/IGNITE-2896 Project: Ignite

[jira] [Created] (IGNITE-2867) IgniteConsistencyException during running load test (cache-atomic-invoke-retry-validator)

Ilya Suntsov created IGNITE-2867: Summary: IgniteConsistencyException during running load test (cache-atomic-invoke-retry-validator) Key: IGNITE-2867 URL: https://issues.apache.org/jira/browse/IGNITE-2867

[jira] [Created] (IGNITE-2638) "Connection to Ignite Web Agent is not established" form not in focus

Ilya Suntsov created IGNITE-2638: Summary: "Connection to Ignite Web Agent is not established" form not in focus Key: IGNITE-2638 URL: https://issues.apache.org/jira/browse/IGNITE-2638

[jira] [Created] (IGNITE-2327) No error message when visorui connects to sequre grid without permissions

Ilya Suntsov created IGNITE-2327: Summary: No error message when visorui connects to sequre grid without permissions Key: IGNITE-2327 URL: https://issues.apache.org/jira/browse/IGNITE-2327 Project

Re: Mandatory requirement to run ExampleNodeStartup only for a several examples

> > > > DO NOT ALLOW to start remote nodes via ignite.sh out of the box, but > if > > > > user put example cache store factory class into \libs folder example > > will > > > > run. > > > > > > > > >> > > > > > > > > > > > > > > org.apache.ignite.examples.binary.datagrid.store.auto.CacheBinaryAutoStoreExample > > > > This example ALLOW to start remote nodes via ignite.sh. > > > > > > > > -- > > > > Alexey Kuznetsov > > > > GridGain Systems > > > > www.gridgain.com > > > > > > > > > > > > > > > -- > > Alexey Kuznetsov > > GridGain Systems > > www.gridgain.com > > > -- Ilya Suntsov

[jira] [Created] (IGNITE-2175) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7)

Ilya Suntsov created IGNITE-2175: Summary: Not valid exceptions in case when example can't works with remote node started with server classpath (Java 7) Key: IGNITE-2175 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-2158) Null values in examples output

Ilya Suntsov created IGNITE-2158: Summary: Null values in examples output Key: IGNITE-2158 URL: https://issues.apache.org/jira/browse/IGNITE-2158 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-2128) Incorrect output in CacheClientBinaryQueryExample

Ilya Suntsov created IGNITE-2128: Summary: Incorrect output in CacheClientBinaryQueryExample Key: IGNITE-2128 URL: https://issues.apache.org/jira/browse/IGNITE-2128 Project: Ignite Issue

[jira] [Created] (IGNITE-2078) Need to clean cache after query in CacheQueryExample

Ilya Suntsov created IGNITE-2078: Summary: Need to clean cache after query in CacheQueryExample Key: IGNITE-2078 URL: https://issues.apache.org/jira/browse/IGNITE-2078 Project: Ignite Issue

[jira] [Created] (IGNITE-2041) CacheAutoStoreExample: Failed to find class with given class loader for unmarshalling

Ilya Suntsov created IGNITE-2041: Summary: CacheAutoStoreExample: Failed to find class with given class loader for unmarshalling Key: IGNITE-2041 URL: https://issues.apache.org/jira/browse/IGNITE-2041

[jira] [Created] (IGNITE-2034) Need to print information about marshaller in log (for yardstick-ignite)

Ilya Suntsov created IGNITE-2034: Summary: Need to print information about marshaller in log (for yardstick-ignite) Key: IGNITE-2034 URL: https://issues.apache.org/jira/browse/IGNITE-2034 Project

[jira] [Created] (IGNITE-2035) Misprint in javadoc

Ilya Suntsov created IGNITE-2035: Summary: Misprint in javadoc Key: IGNITE-2035 URL: https://issues.apache.org/jira/browse/IGNITE-2035 Project: Ignite Issue Type: Bug Components

[jira] [Created] (IGNITE-2024) CacheAutoStoreExample: Failed to execute compound future reducer

Ilya Suntsov created IGNITE-2024: Summary: CacheAutoStoreExample: Failed to execute compound future reducer Key: IGNITE-2024 URL: https://issues.apache.org/jira/browse/IGNITE-2024 Project: Ignite