Re: [jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS

Hello Prachi! I reassigned issue https://issues.apache.org/jira/browse/IGNITE-4052 to you to approve changes of page - https://apacheignite.readme.io/docs/mesos-deployment#section-ignite-mesos-framework Vadim 2017-05-11 11:54 GMT+03:00 Вадим Опольский : > Hello guys! > >

[GitHub] ignite pull request #1937: IGNITE-2492 .NET: Peer assembly loading

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1937 IGNITE-2492 .NET: Peer assembly loading You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-2492 Alternatively you can

[jira] [Created] (IGNITE-5213) .NET: Reflective serializer fails on custom dictionaries

Pavel Tupitsyn created IGNITE-5213: -- Summary: .NET: Reflective serializer fails on custom dictionaries Key: IGNITE-5213 URL: https://issues.apache.org/jira/browse/IGNITE-5213 Project: Ignite

[GitHub] ignite pull request #1934: Ignite 5112

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

IGNITE-4447

Hi guys! Vladimir, is issue https://issues.apache.org/jira/browse/IGNITE-4447 actual now? Which tests do u mean? Detail please. Vadim

[jira] [Created] (IGNITE-5214) ConcurrentModificationException with enable DEBUG log level

Nikolay Tikhonov created IGNITE-5214: Summary: ConcurrentModificationException with enable DEBUG log level Key: IGNITE-5214 URL: https://issues.apache.org/jira/browse/IGNITE-5214 Project: Ignite

[GitHub] ignite pull request #1936: Fixed segmented indices snapshots.

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1936 Fixed segmented indices snapshots. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gg-12171 Alternatively you can

Re: Data compression in Ignite 2.0

Hi, Igniters! Apache 2.0 is released. Let's continue the discussion about a compression design. At the moment, I found only one solution which is compatible with querying and indexing, this is per-objects-field compression. Per-fields compression means that metadata (a header) of an object

[GitHub] ignite pull request #1938: IGNITE-5215: Allow user to configure memory polic...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/1938 IGNITE-5215: Allow user to configure memory policy with maxSize lesse… You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-5216) Add Stream API support to Ignite ML matrices.

Yury Babak created IGNITE-5216: -- Summary: Add Stream API support to Ignite ML matrices. Key: IGNITE-5216 URL: https://issues.apache.org/jira/browse/IGNITE-5216 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5217) Gradient descent

Yury Babak created IGNITE-5217: -- Summary: Gradient descent Key: IGNITE-5217 URL: https://issues.apache.org/jira/browse/IGNITE-5217 Project: Ignite Issue Type: Task Components: ml

[jira] [Created] (IGNITE-5220) Partial derivatives calculation.

Yury Babak created IGNITE-5220: -- Summary: Partial derivatives calculation. Key: IGNITE-5220 URL: https://issues.apache.org/jira/browse/IGNITE-5220 Project: Ignite Issue Type: New Feature

[jira] [Created] (IGNITE-5222) .NET: LINQ does not support IndexOf with char overloads

Pavel Tupitsyn created IGNITE-5222: -- Summary: .NET: LINQ does not support IndexOf with char overloads Key: IGNITE-5222 URL: https://issues.apache.org/jira/browse/IGNITE-5222 Project: Ignite

Re: Ignite ML, next steps (IGNITE-5029)

Update: Here's the last batch of ml related tickets for next a few months: * Add Stream API support to Ignite ML matrices, IGNITE-5216 . * Gradient descent, IGNITE-5217 . * Decision trees,

[jira] [Created] (IGNITE-5223) Allow use local binary metadata cache if it's possible

Dmitry Karachentsev created IGNITE-5223: --- Summary: Allow use local binary metadata cache if it's possible Key: IGNITE-5223 URL: https://issues.apache.org/jira/browse/IGNITE-5223 Project: Ignite

[jira] [Created] (IGNITE-5224) .NET: PadLeft and PadRight support in LINQ

Pavel Tupitsyn created IGNITE-5224: -- Summary: .NET: PadLeft and PadRight support in LINQ Key: IGNITE-5224 URL: https://issues.apache.org/jira/browse/IGNITE-5224 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-5215) Allow user to configure memory policy with maxSize lesser than default initialSize

Ivan Rakov created IGNITE-5215: -- Summary: Allow user to configure memory policy with maxSize lesser than default initialSize Key: IGNITE-5215 URL: https://issues.apache.org/jira/browse/IGNITE-5215

[jira] [Created] (IGNITE-5218) Decision trees

Yury Babak created IGNITE-5218: -- Summary: Decision trees Key: IGNITE-5218 URL: https://issues.apache.org/jira/browse/IGNITE-5218 Project: Ignite Issue Type: Task Components: ml

Re: ignite-5097 is ready for review (BinaryMarshaller should write ints in "varint" encoding where it makes sense)

Any thoughts about implemented solution? 2017-05-04 13:26 GMT+03:00 Vyacheslav Daradur : > Hi Igniteres! > > Java part is ready for review. > > BinaryMarshaller should write ints in "varint" encoding where it makes > sense

[GitHub] ignite pull request #1939: Ignite 5223 Allow use local binary metadata cache...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1939 Ignite 5223 Allow use local binary metadata cache if it's possible You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1940: Ignite 2.0 Tests suite check

Github user dspavlov closed the pull request at: https://github.com/apache/ignite/pull/1940 --- 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 #1943: Ignite-4938, teamcity run on 2.0 run configs

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/1943 Ignite-4938, teamcity run on 2.0 run configs For run on TC, don't merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite

[GitHub] ignite pull request #1940: Ignite 2.0 Tests suite check

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/1940 Ignite 2.0 Tests suite check You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite master Alternatively you can review and apply

Store data from Python in multiple caches using Redis or Memcached client in Apache ignite

Examples at following link displays how data is stored in default caches(single cache) only in Apache Ignite: https://apacheignite.readme.io/docs/redis#python https://apacheignite.readme.io/v1.8/docs/memcached-support

Re: Data compression in Ignite 2.0

I created the ticket: https://issues.apache.org/jira/browse/IGNITE-5226 I'll prepare a PR with described solution in couple of days. 2017-05-15 15:05 GMT+03:00 Vyacheslav Daradur : > Hi, Igniters! > > Apache 2.0 is released. > > Let's continue the discussion about a

[GitHub] ignite pull request #1942: IGNITE-5225: Fixed thread pools incorrect shutdow...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1942 IGNITE-5225: Fixed thread pools incorrect shutdown. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5225

[GitHub] ignite pull request #1944: IGNITE-4831 fixed (Add an option to disable MBean...

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

Re: Data compression in Ignite 2.0

Dmitriy, I have ready prototype. I want to show it. It is always easier to discuss on example. 2017-05-15 19:02 GMT+03:00 Dmitriy Setrakyan : > Vyacheslav, > > I think it is a bit premature to provide a PR without getting a community > consensus on the dev list. Please

[GitHub] ignite pull request #1945: IGNITE-4831 fixed (Add an option to disable MBean...

GitHub user rfqu opened a pull request: https://github.com/apache/ignite/pull/1945 IGNITE-4831 fixed (Add an option to disable MBeans). Option IGNITE_DI… …SABLE_MBEANS added. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1946: Ignite 5131

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

[GitHub] ignite pull request #1944: IGNITE-4831 fixed (Add an option to disable MBean...

GitHub user rfqu opened a pull request: https://github.com/apache/ignite/pull/1944 IGNITE-4831 fixed (Add an option to disable MBeans). Option IGNITE_DI… …SABLE_MBEANS added. You can merge this pull request into a Git repository by running: $ git pull

Re: Apache Ignite 2.1 scope

Well, let me propose the following milestones for 2.1 release then. Code freeze: June 2nd. Final QA and benchmarking: June 5 - June 8 Voting: ~ June 9 Release: ~ June 13 Also I heard H2 has to be released once again to support Ignite’s CREATE table command. Think that we should talk to H2 folks

[jira] [Created] (IGNITE-5226) Annotated fields compression

Vyacheslav Daradur created IGNITE-5226: -- Summary: Annotated fields compression Key: IGNITE-5226 URL: https://issues.apache.org/jira/browse/IGNITE-5226 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-5227) StackOverflowError in GridCacheMapEntry#checkOwnerChanged()

Alexey Goncharuk created IGNITE-5227: Summary: StackOverflowError in GridCacheMapEntry#checkOwnerChanged() Key: IGNITE-5227 URL: https://issues.apache.org/jira/browse/IGNITE-5227 Project: Ignite

[GitHub] ignite pull request #1941: Ignite-4938, teamcity run on 2.0 run configs

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/1941 Ignite-4938, teamcity run on 2.0 run configs For run on TC, don't merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite

[GitHub] ignite pull request #1941: Ignite-4938, teamcity run on 2.0 run configs

Github user dspavlov closed the pull request at: https://github.com/apache/ignite/pull/1941 --- 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-5228) Console: Failed to collect events in process of log command

Vasiliy Sisko created IGNITE-5228: - Summary: Console: Failed to collect events in process of log command Key: IGNITE-5228 URL: https://issues.apache.org/jira/browse/IGNITE-5228 Project: Ignite

[GitHub] ignite pull request #1947: IGNITE-1456: CPP: Implements Cache.Rebalance()

GitHub user vinx13 opened a pull request: https://github.com/apache/ignite/pull/1947 IGNITE-1456: CPP: Implements Cache.Rebalance() You can merge this pull request into a Git repository by running: $ git pull https://github.com/vinx13/ignite ignite-1456 Alternatively you can

Re: ignite-5097 is ready for review (BinaryMarshaller should write ints in "varint" encoding where it makes sense)

As I see the discussion is happening in JIRA. BTW, can we do this improvement without breaking compatibility with 2.0? — Denis > On May 15, 2017, at 5:08 AM, Vyacheslav Daradur wrote: > > Any thoughts about implemented solution? > > 2017-05-04 13:26 GMT+03:00 Vyacheslav

Re: Ignite ML, next steps (IGNITE-5029)

Hi, >From my point of view it's IGNITE-5113(k-means), IGNITE-5109(already done), IGNITE-5114(optimized distributed matrix arithmetic), IGNITE-5102(fix for fold/map behaviour) for sure and possibly the IGNITE-5059(Logistic regression) if we will have enough time before code freeze. Regards, Yury

Re: Apache Ignite 2.1 scope

Looks a little tight. Let's hope we can make it. On Mon, May 15, 2017 at 1:29 PM, Denis Magda wrote: > Well, let me propose the following milestones for 2.1 release then. > > Code freeze: June 2nd. > Final QA and benchmarking: June 5 - June 8 > Voting: ~ June 9 > Release: ~

Re: Data compression in Ignite 2.0

Vyacheslav, I think it is a bit premature to provide a PR without getting a community consensus on the dev list. Please allow some time for the community to respond. D. On Mon, May 15, 2017 at 6:36 AM, Vyacheslav Daradur wrote: > I created the ticket:

Re: Store data from Python in multiple caches using Redis or Memcached client in Apache ignite

Hi, see below > On May 15, 2017, at 7:32 AM, rishi007bansod wrote: > > Examples at following link displays how data is stored in default > caches(single cache) only in Apache Ignite: > > https://apacheignite.readme.io/docs/redis#python >

Re: GridGain Donates Persistent Distributed Store To ASF (Apache Ignite)

The receipt of the software grant (the persistent store) was acknowledged by Craig Russel. Now, we need to move on with this > In the meanwhile, I’ve prepared the IP Clearance page referring to the > template below but failed to commit the changes to ASF repo: >

Re: Ignite ML, next steps (IGNITE-5029)

Looks good, thanks for the update! Yuri, what do you think can be done in 2.1 time frame. This release should be rolled out ~ in the mid of June. — Denis > On May 15, 2017, at 5:19 AM, Yury Babak wrote: > > Update: > > Here's the last batch of ml related tickets for next

[GitHub] ignite pull request #1948: IGNITE-2190:

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/1948 IGNITE-2190: * Added GridCacheEmptyScanQueryTest to reproduce bug described in task * Test succeed for a OptimizedMarshaller but fails for a BinaryMarshaller * Minor fixes in

Re: Store data from Python in multiple caches using Redis or Memcached client in Apache ignite

Denis, yes, I would like to enable switching caches via "CONFIG SET parameter value".I created https://issues.apache.org/jira/browse/IGNITE-5229 for this, and will discuss it in a separate thread. Roman On Tuesday, May 16, 2017 8:45 AM, Denis Magda wrote: Hi, see

[jira] [Created] (IGNITE-5229) Specify caches when using Redis protocol

Roman Shtykh created IGNITE-5229: Summary: Specify caches when using Redis protocol Key: IGNITE-5229 URL: https://issues.apache.org/jira/browse/IGNITE-5229 Project: Ignite Issue Type: