Re: IGNITE-13

Hi Vadim, I'm not sure I understand your benchmarks and how they verify the optimization discussed here. Basically, here is what needs to be done: 1. Create a benchmark for BinaryWriterExImpl#doWriteString method. 2. Run the benchmark with current implementation. 3. Make the change described in

Re: Entry filter in IgniteCache#loadCache

On Sat, Feb 18, 2017 at 12:51 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > Currently IgniteCache.loadCache has optional entry filter that can be > passed as an argument. It seems to be redundant because: > >- Filtering that is done by this filter can be as

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

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1556 IGNITE-4106: SQL: parallelize sql queries over cache local partitions Merged with IGNITE-1.9. You can merge this pull request into a Git repository by running: $ git pull

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

Github user AMashenkov closed the pull request at: https://github.com/apache/ignite/pull/1278 --- 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

[jira] [Created] (IGNITE-4730) .NET: Propagate IgniteConfiguration.OdbcConfiguration

Pavel Tupitsyn created IGNITE-4730: -- Summary: .NET: Propagate IgniteConfiguration.OdbcConfiguration Key: IGNITE-4730 URL: https://issues.apache.org/jira/browse/IGNITE-4730 Project: Ignite

Clean sitemap.xml for the website

Hello Igniters, Based on the SEO analysis we reported earlier, I have cleaned up the sitemap.xml for the website, maintaining the amount of URLs to the minimum recommended. I am attaching a patch with all the changes Could any of the committers please apply this patch to the website repo?

Re: IGNITE-13

Hello everybody! https://issues.apache.org/jira/browse/IGNITE-13 Valentin, I just have finished benchmark (with JMH) - https://github.com/javaller/MyBenchmark.git It collect data about time working of serialization. For instance -

[jira] [Created] (IGNITE-4729) Async operation support in platform plugins

Pavel Tupitsyn created IGNITE-4729: -- Summary: Async operation support in platform plugins Key: IGNITE-4729 URL: https://issues.apache.org/jira/browse/IGNITE-4729 Project: Ignite Issue Type:

general question

Hi! Why local deployment SPI is ignored, if peer class loading is disabled, and local deployment spi is enabled ? -- *Best Regards,* *Kuznetsov Aleksey*

IGNITE-824: [Test] GridRandomSelfTest # testPerformance was disabled.

Do we still need this test? Can I remove it?

[jira] [Created] (IGNITE-4728) Web Console: Remember the screen from which user has left the previous session.

Vica Abramova created IGNITE-4728: - Summary: Web Console: Remember the screen from which user has left the previous session. Key: IGNITE-4728 URL: https://issues.apache.org/jira/browse/IGNITE-4728

[jira] [Created] (IGNITE-4727) Web Console: Fix the position of tooltips in modal windows

Vica Abramova created IGNITE-4727: - Summary: Web Console: Fix the position of tooltips in modal windows Key: IGNITE-4727 URL: https://issues.apache.org/jira/browse/IGNITE-4727 Project: Ignite

Re: IGNITE-1948 ClusterTopologyCheckedException can return null for retryReadyFuture()

Alexey, I'm ready to make some conclusions. You can see result immediately here: PR: https://github.com/apache/ignite/pull/1537/files CI Tests: http://ci.ignite.apache.org/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull/1537/head I fixed only

Re: Locking of partition with affinityRun/affinityCall

Denis, I've fixed javadocs for affinityRun/affinityCall. Please review the changes at the PR: https://github.com/apache/ignite/pull/1550 On 08.12.2016 12:06, Taras Ledkov wrote: Denis, The second point is absolutely correct. The rebalancing isn't blocked. The partition will not be evicted

Re: Entry filter in IgniteCache#loadCache

+1 On Sat, Feb 18, 2017 at 11:51 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > Currently IgniteCache.loadCache has optional entry filter that can be > passed as an argument. It seems to be redundant because: > >- Filtering that is done by this filter can be

[GitHub] ignite pull request #521: comm balance debug

Github user yzhdanov closed the pull request at: https://github.com/apache/ignite/pull/521 --- 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-4726) SQL: benchmark DML operations

Vladimir Ozerov created IGNITE-4726: --- Summary: SQL: benchmark DML operations Key: IGNITE-4726 URL: https://issues.apache.org/jira/browse/IGNITE-4726 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1447: IGNITE-4157 mapping updates notification hook

Github user sergey-chugunov-1985 closed the pull request at: https://github.com/apache/ignite/pull/1447 --- 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

Re: Apache Ignite 1.9

Igniters, Code freeze date changed to Feb 20 19-00 MSK. Since that time, each fix should be allowed at this thread before push. On Mon, Feb 20, 2017 at 1:50 PM, Vladimir Ozerov wrote: > Igniters, > > IGNITE-4169 [1] (streaming in DML) has been merged to 1.9 branch. > >

[GitHub] ignite pull request #1554: IGNITE-4409 UUID literals handling.

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/1554 IGNITE-4409 UUID literals handling. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4409 Alternatively

Re: IGNITE-3422 - ready for review

Hi Vyacheslav, Thank you for contribution. I reviewed implementation again and now I am in doubts whether our product would really benefit from it or not. See my comments in the ticket. I'de prefer Denis Magda to chime in and give his feedback first. Vladimir. On Wed, Feb 15, 2017 at 5:00 PM,

Re: Apache Ignite 1.9

Igniters, IGNITE-4169 [1] (streaming in DML) has been merged to 1.9 branch. [1] https://issues.apache.org/jira/browse/IGNITE-4169 On Fri, Feb 17, 2017 at 4:01 PM, Anton Vinogradov wrote: > https://issues.apache.org/jira/browse/IGNITE-3862 > already at 1.9, fixed

[jira] [Created] (IGNITE-4725) Document streaming mode for JDBC driver

Vladimir Ozerov created IGNITE-4725: --- Summary: Document streaming mode for JDBC driver Key: IGNITE-4725 URL: https://issues.apache.org/jira/browse/IGNITE-4725 Project: Ignite Issue Type:

Re: Ignite 1.8 c++ Platform installation issue

Well, this is another issue. It has been fixed already, but still affects 1.8.0 source release. As a workaround for now you can use sources from Git repository 1.8.0 tag [1], or you can only get missing apache-ignite-1.8.0-src/modules/platforms/cpp/core/include/

Re: Ignite 1.8 c++ Platform installation issue

Hi, If I ignore that and continue with the process of installation with 'make' command, here is the error I get. make[3]: Entering directory './apache-ignite-1.8.0-src/modules/platforms/cpp/core/include' make[3]: *** No rule to make target 'ignite/impl/interop/interop_target.h', needed by

[jira] [Created] (IGNITE-4724) AVG function always returns double type instead of the argument type

Sergey Kozlov created IGNITE-4724: - Summary: AVG function always returns double type instead of the argument type Key: IGNITE-4724 URL: https://issues.apache.org/jira/browse/IGNITE-4724 Project:

Re: Ignite 1.8 c++ Platform installation issue

Hi, This is not an error. It comes from the Automake buildsystem considers files named "core" to be a coredumps and tries to remove them. Ignite C++ has library named "core" with corresponding directory. Shortly speaking, just ignore this message. Best Regards, Igor On Sun, Feb 19, 2017 at

[jira] [Created] (IGNITE-4723) .NET: Support REGEXP_LIKE in LINQ

Pavel Tupitsyn created IGNITE-4723: -- Summary: .NET: Support REGEXP_LIKE in LINQ Key: IGNITE-4723 URL: https://issues.apache.org/jira/browse/IGNITE-4723 Project: Ignite Issue Type:

Re: [jira] [Created] (IGNITE-4680) Properly split batch atomic cache operations between stripes (putAll, removeAll, etc)

Konstantin, please go ahead. --Yakov 2017-02-11 20:18 GMT+03:00 Константин Дудков : > Yakov, > > If you don't mind I would like to do this ticket. > > 10.02.2017, 16:31, "Yakov Zhdanov (JIRA)" : > > Yakov Zhdanov created IGNITE-4680: > >

[jira] [Created] (IGNITE-4722) CacheRandomOperation benchmark: preloading as separate benchmarl with ability to load in a loop

Ksenia Rybakova created IGNITE-4722: --- Summary: CacheRandomOperation benchmark: preloading as separate benchmarl with ability to load in a loop Key: IGNITE-4722 URL:

Will take IGNITE-1264 Resource SPI

will take https://issues.apache.org/jira/browse/IGNITE-1264 -- *Best Regards,* *Kuznetsov Aleksey*

Re: cache metadata progapagation

Dmitriy, What do you mean by deploying cache metadata? The node filter itself must be deserialized on each node because we need to evaluate it. As for the CacheConfiguration, we do not need to deserialize the configuration on every node, this will be a good change for Ignite 2.0. 2017-02-16

Re: PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Thanks, Aleksey, I will take a look this week. --AG 2017-02-20 10:25 GMT+03:00 ALEKSEY KUZNETSOV : > Hi! Review my PR again, plz - https://github.com/apache/ignite/pull/1517 > > пт, 17 февр. 2017 г. в 14:44, ALEKSEY KUZNETSOV >: > > >