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

[nizhikov]

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 IgniteProcessProxy and GridAbstractTest for a possibility 
to modify separate jvm grid classpath
* Added ignite-2190-1.0.jar to binary dependencies(source can be obtained 
from https://github.com/nizhikov/ignite-2190-binary)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nizhikov/ignite ignite-2190

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1948.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1948


commit 1857a95185266e256b269897e577cae18db7a577
Author: Ижиков Николай Владимирович 

Date:   2017-05-16T05:57:02Z

IGNITE-2190:

* Added GridCacheEmptyScanQueryTest to reproduce bug described in task
* Test succeed for a OptimizedMarshaller but fails for a BinaryMarshaller
* Minor fixes in IgniteProcessProxy and GridAbstractTest for a possibility 
to modify separate jvm grid classpath
* Added ignite-2190-1.0.jar to binary dependencies(source can be obtained 
from https://github.com/nizhikov/ignite-2190-binary)




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[Roman Shtykh]

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 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
>   
> 
According to the docs there is no way to store data in multiple caches for now.

*Roman*, do you have any plans to remove the limitation in the nearest releases?

> https://apacheignite.readme.io/v1.8/docs/memcached-support
>   
> 

*Val*, is this achievable with Memcached client? I can’t find a hint how to do 
this.

> I want to store data in multiple caches(with different cache names) in
> Apache Ignite from Python either using redis client or using memcache
> client. How can I do this? Also, are SQL queries supported when we use
> Memcached or redis client for caching data in Ignite from Python.
> 

If you want to use SQL queries from Python then I would suggest connecting to 
the cluster with ODBC driver:
https://apacheignite.readme.io/docs/odbc-driver

For instance, this is how it works from PHP and the same can be easily done 
from Python side:
https://apacheignite-mix.readme.io/docs/php-pdo

—
Denis

> 
> 
> --
> View this message in context: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Store-data-from-Python-in-multiple-caches-using-Redis-or-Memcached-client-in-Apache-ignite-tp17660.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.


   

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

[Roman Shtykh (JIRA)]

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: Improvement
Affects Versions: 2.0
Reporter: Roman Shtykh
Assignee: Roman Shtykh






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5228) Console: Failed to collect events in process of log command

[Vasiliy Sisko (JIRA)]

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
  Issue Type: Bug
Reporter: Vasiliy Sisko


# Run node and connect Visor console.
# Start logging by command: log -l -f=1.txt

On node exception is thrown.
{code}
class org.apache.ignite.IgniteException: Failed to query events because default 
no-op event storage SPI is used. Consider configuring MemoryEventStorageSpi or 
another EventStorageSpi implementation via 
IgniteConfiguration.setEventStorageSpi() configuration property.
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:949)
at 
org.apache.ignite.internal.IgniteEventsImpl.localQuery(IgniteEventsImpl.java:251)
at 
org.apache.ignite.internal.visor.node.VisorNodeEventsCollectorTask$VisorNodeEventsCollectorJob.run(VisorNodeEventsCollectorTask.java:176)
at 
org.apache.ignite.internal.visor.node.VisorNodeEventsCollectorTask$VisorNodeEventsCollectorJob.run(VisorNodeEventsCollectorTask.java:72)
at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6621)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1114)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1907)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1257)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:885)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:114)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:802)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to query 
events because default no-op event storage SPI is used. Consider configuring 
MemoryEventStorageSpi or another EventStorageSpi implementation via 
IgniteConfiguration.setEventStorageSpi() configuration property.
at 
org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.localEvents(GridEventStorageManager.java:913)
at 
org.apache.ignite.internal.IgniteEventsImpl.localQuery(IgniteEventsImpl.java:248)
... 17 more
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[vinx13]

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 review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1947.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1947


commit 0bb53d8e8e908dad703b2c612bbfca8313ee80cb
Author: Wuwei Lin 
Date:   2017-05-16T01:36:25Z

CPP: Implements Cache.Rebalance()




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Apache Ignite 2.1 scope

[Dmitriy Setrakyan]

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: ~ 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 to make it happen in
> June 22nd - June 2nd time frame.
>
> —
> Denis
>
> > On May 11, 2017, at 2:26 AM, Pavel Tupitsyn 
> wrote:
> >
> > As for .NET, I would propose to concentrate on peer deployment
> (IGNITE-2492)
> > and related stuff, like IGNITE-1894 .NET: Delegate support in the API via
> > extension methods.
> >
> > SQL Dependency does not look important to me, we can reschedule it for
> > later versions.
> >
> > On Thu, May 11, 2017 at 12:01 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> >> Vyacheslav, I think it is worth the research, but you should always keep
> >> data querying and indexing in mind. For example, I don't see how by-page
> >> compression will solve it.
> >>
> >> On Thu, May 11, 2017 at 1:52 AM, Vyacheslav Daradur <
> daradu...@gmail.com>
> >> wrote:
> >>
> >>> Dmitriy,
> >>>
> >>> I'm researching a best way for this future.
> >>>
> >>> At the moment I found only one way (querying and indexing compatible),
> >> this
> >>> is per-objects-field compression.
> >>>
> >>> But there is a good proffit only for long strings or fields with large
> >>> objects.
> >>>
> >>> Maybe it makes sense just to introduce compression for string fileds.
> >>>
> >>> I'm researching the new page-memory architecture as applied to by-page
> >>> compression.
> >>>
> >>> 2017-05-11 11:30 GMT+03:00 Dmitriy Setrakyan :
> >>>
>  On Thu, May 11, 2017 at 12:44 AM, Vyacheslav Daradur <
> >>> daradu...@gmail.com>
>  wrote:
> 
> > Denis,
> >
> > The described roadmap looks great!
> >
> > Additional, I vote for introducing an ability (OOTB) to store objects
> >>> in
>  a
> > cache in a compressed form.
> > This will allow to store more data at the cost of incriasing of CPU
> > utilization.
> >
> 
>  One of the problems with compression is indexing and querying. How do
> >> we
>  index the data if it is compressed?
> 
> 
> >
> >
> > 2017-05-11 4:23 GMT+03:00 Denis Magda :
> >
> >> Igniters,
> >>
> >> Let me start a discussion around the scope for 2.1 release.
> >>
> >> In my vision the main direction of our ongoing efforts should be
> >> implementing in life a use case of Ignite as a transactional
>  distributed
> >> SQL database and HTAP platform. The current use cases (database
> >>> cache,
> > data
> >> grid, micro services platform, etc.) will be supported as usual, no
> > changes
> >> on that frontier.
> >>
> >> Keeping this in mind, the roadmap needs to include essential SQL
>  related
> >> features as well as disk based capabilities, MVCC support, advanced
> >>> DDL
> >> implementation and so on so forth. This is for Ignite as a SQL
>  database.
> >>
> >> Next, Machine Learning will be a great addition to Ignite as an
> >> HTAP
> >> platform offering. This is why we should keep investing our time
> >> and
> >> resources in that recently released component.
> >>
> >> Having this said, I see the scope for 2.1 release this way:
> >>
> >> 1. Distributed Persistent Store - if the donation is accepted by
> >> ASF.
>  The
> >> decision is to be done in separate discussion. W/o the store
> >>   Ignite can only be used as In-Memory SQL database.
> >>
> >> 2. SQL Grid:
> >>- CREATE & DROP table commands: https://issues.apache.org/
> >> jira/browse/IGNITE-4651
> >>- Renewed JDBC driver: https://issues.apache.org/
> >> jira/browse/IGNITE-4922
> >>- Collocation based routing of SQL queries:
> > https://issues.apache.org/
> >> jira/browse/IGNITE-4510,
> >>   https://issues.apache.org/jira/browse/IGNITE-4509
> >>-
> >>
> >> 3. .NET:
> >>- Peer-class loading: https://issues.apache.org/
> >> jira/browse/IGNITE-2492
> >>- SQLDependency: https://issues.apache.org/
> >>> jira/browse/IGNITE-2657
> >>
> >> 4. C++:
> >>- Compute Grid: https://issues.apache.org/
> >>> jira/browse/IGNITE-3574
> >>
> >> 5. ML Grid:
> >>- Linear regression algorithms: https://issues.apache.org/
> >> jira/browse/IGNITE-5012
> >>- K-means clustering: https://issues.apache.org/
> >> jira/browse/IGNITE-5113
> >>
> >>
> >> Please join the thread and share your thoughts, ideas and concerns.
> >>
> >> —
> >> Denis
> >>
> >>
> >>
> >
> >
> >
> >
> > --
> 

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

[Yury Babak]

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



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-ML-next-steps-IGNITE-5029-tp17096p17676.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

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

[Denis Magda]

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 Daradur :
> 
>> Hi Igniteres!
>> 
>> Java part is ready for review.
>> 
>> BinaryMarshaller should write ints in "varint" encoding where it makes
>> sense 
>> ci.tests 
>> PR 
>> 
>> 
>> --
>> Best Regards, Vyacheslav
>> 
> 
> 
> 
> -- 
> Best Regards, Vyacheslav

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

[Denis Magda]

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 a few months:
> 
> * Add Stream API support to Ignite ML matrices,  IGNITE-5216
>   .
> * Gradient descent,  IGNITE-5217
>   .
> * Decision trees,  IGNITE-5218
>   .
> * Generalization of cost function for Linear Regression,  IGNITE-5219
>   .
> * Investigate possibility of integrating with dl4j,  IGNITE-5221
>   .
> 
> Regards,
> Yury Babak. 
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-ML-next-steps-IGNITE-5029-tp17096p17651.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

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

[Denis Magda]

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
>   
> 
According to the docs there is no way to store data in multiple caches for now.

*Roman*, do you have any plans to remove the limitation in the nearest releases?

> https://apacheignite.readme.io/v1.8/docs/memcached-support
>   
> 

*Val*, is this achievable with Memcached client? I can’t find a hint how to do 
this.

> I want to store data in multiple caches(with different cache names) in
> Apache Ignite from Python either using redis client or using memcache
> client. How can I do this? Also, are SQL queries supported when we use
> Memcached or redis client for caching data in Ignite from Python.
> 

If you want to use SQL queries from Python then I would suggest connecting to 
the cluster with ODBC driver:
https://apacheignite.readme.io/docs/odbc-driver

For instance, this is how it works from PHP and the same can be easily done 
from Python side:
https://apacheignite-mix.readme.io/docs/php-pdo

—
Denis

> 
> 
> --
> View this message in context: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Store-data-from-Python-in-multiple-caches-using-Redis-or-Memcached-client-in-Apache-ignite-tp17660.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

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

[Denis Magda]

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:
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
> 
> *Roman S.*, *Cos*, could you help me with this by granting karma or 
> committing the form from under your account?

Roman, Cos, could you help with this?

*Alex G.*, please add Apache 2.0 copyrights to all source files that are going 
to be donated. Presently there is no copyright at all.

Everyone interested please spend some time exploring the store's docs and 
sources shared in my previous email. If no one has any concerns I will proceed 
with the donation formalities.

—
Denis

> On May 12, 2017, at 2:59 PM, Denis Magda  wrote:
> 
> Folks,
> 
> The repository with the donation is ready and available for review:
> https://github.com/agoncharuk/ignite/tree/pds-donate
> 
> Big and main part of the sources is aggregated in “modules/pds”. The rest, 
> that connects Apache Ignite memory architecture and SQL engine is under 
> “core” and “indexing” modules. Alex Goncharuk should be able to point to 
> specific files or commits if required.
> 
> Here is a description:
> * Persistent Store Overview: 
> https://cwiki.apache.org/confluence/display/IGNITE/Persistent+Store+Overview
> * Persistent Store Internal Design: 
> https://cwiki.apache.org/confluence/display/IGNITE/Persistent+Store+Internal+Design
> 
> The SGA will be signed and sent on Monday.
> 
> In the meanwhile, I’ve prepared the IP Clearance page referring to the 
> template below but failed to commit the changes to ASF repo:
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
> 
> *Roman S.*, *Cos*, could you help me with this by granting karma or 
> committing the form from under your account?
> 
> —
> Denis
> 
>> On Apr 25, 2017, at 9:56 AM, Konstantin Boudnik  wrote:
>> 
>> While no one is suggesting an IP trap laid out in the non-SGA'ed code
>> in this particular case, we don't want to setup a precedent like this.
>> 
>> From the overall ASF perspective I +1 what Roman has just said.
>> 
>> Thanks,
>> --
>> Take care,
>> Konstantin (Cos) Boudnik
>> 
>> 
>> On Wed, Apr 19, 2017 at 11:41 PM, Roman Shaposhnik  
>> wrote:
>>> On Wed, Apr 19, 2017 at 6:21 PM, Dmitriy Setrakyan
>>>  wrote:
 On Wed, Apr 19, 2017 at 6:00 PM, Konstantin Boudnik  
 wrote:
 
> On Tue, Apr 18, 2017 at 11:54PM, Dmitriy Setrakyan wrote:
>> 
>> Would a standard SGA suffice here?
>> 
>> I believe that ASF guidelines suggest that a discussion should happen
>> first. Once the community gets enough information, we will move to a PMC
>> vote. I was under the impression that once the PMC vote passes, then the
>> SGA should be provided. Or does GridGain need to provide a signed SGA
> right
>> away?
> 
> That reminds me of that Pelosi's self-inflicted conundrum of "In order
> to see the bill, we should pass the bill" ;)
> 
 
 Haha :)
 
 SGA != code. In my view, the code should be provided to the community for a
 review. But I am struggling to see why should an SGA be signed prior to the
 community accepting the donation.
>>> 
>>> There's no such thing as SGA without a reference to a code base.
>>> 
>>> Also, as I explained -- as a community member I would refuse to look
>>> at the code base that doesn't have a proper licensing attached to it.
>>> SGA established this kind of proper licensing.
>>> 
>>> Now, SGA is deinetly not the only way to do so, but it is the easiest
>>> and since you'd have to do it anyway the most convenient for the
>>> community.
>>> 
>>> Thanks,
>>> Roman.
> 

Re: Apache Ignite 2.1 scope

[Denis Magda]

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 to make it happen in June 22nd - 
June 2nd time frame.

—
Denis

> On May 11, 2017, at 2:26 AM, Pavel Tupitsyn  wrote:
> 
> As for .NET, I would propose to concentrate on peer deployment (IGNITE-2492)
> and related stuff, like IGNITE-1894 .NET: Delegate support in the API via
> extension methods.
> 
> SQL Dependency does not look important to me, we can reschedule it for
> later versions.
> 
> On Thu, May 11, 2017 at 12:01 PM, Dmitriy Setrakyan 
> wrote:
> 
>> Vyacheslav, I think it is worth the research, but you should always keep
>> data querying and indexing in mind. For example, I don't see how by-page
>> compression will solve it.
>> 
>> On Thu, May 11, 2017 at 1:52 AM, Vyacheslav Daradur 
>> wrote:
>> 
>>> Dmitriy,
>>> 
>>> I'm researching a best way for this future.
>>> 
>>> At the moment I found only one way (querying and indexing compatible),
>> this
>>> is per-objects-field compression.
>>> 
>>> But there is a good proffit only for long strings or fields with large
>>> objects.
>>> 
>>> Maybe it makes sense just to introduce compression for string fileds.
>>> 
>>> I'm researching the new page-memory architecture as applied to by-page
>>> compression.
>>> 
>>> 2017-05-11 11:30 GMT+03:00 Dmitriy Setrakyan :
>>> 
 On Thu, May 11, 2017 at 12:44 AM, Vyacheslav Daradur <
>>> daradu...@gmail.com>
 wrote:
 
> Denis,
> 
> The described roadmap looks great!
> 
> Additional, I vote for introducing an ability (OOTB) to store objects
>>> in
 a
> cache in a compressed form.
> This will allow to store more data at the cost of incriasing of CPU
> utilization.
> 
 
 One of the problems with compression is indexing and querying. How do
>> we
 index the data if it is compressed?
 
 
> 
> 
> 2017-05-11 4:23 GMT+03:00 Denis Magda :
> 
>> Igniters,
>> 
>> Let me start a discussion around the scope for 2.1 release.
>> 
>> In my vision the main direction of our ongoing efforts should be
>> implementing in life a use case of Ignite as a transactional
 distributed
>> SQL database and HTAP platform. The current use cases (database
>>> cache,
> data
>> grid, micro services platform, etc.) will be supported as usual, no
> changes
>> on that frontier.
>> 
>> Keeping this in mind, the roadmap needs to include essential SQL
 related
>> features as well as disk based capabilities, MVCC support, advanced
>>> DDL
>> implementation and so on so forth. This is for Ignite as a SQL
 database.
>> 
>> Next, Machine Learning will be a great addition to Ignite as an
>> HTAP
>> platform offering. This is why we should keep investing our time
>> and
>> resources in that recently released component.
>> 
>> Having this said, I see the scope for 2.1 release this way:
>> 
>> 1. Distributed Persistent Store - if the donation is accepted by
>> ASF.
 The
>> decision is to be done in separate discussion. W/o the store
>>   Ignite can only be used as In-Memory SQL database.
>> 
>> 2. SQL Grid:
>>- CREATE & DROP table commands: https://issues.apache.org/
>> jira/browse/IGNITE-4651
>>- Renewed JDBC driver: https://issues.apache.org/
>> jira/browse/IGNITE-4922
>>- Collocation based routing of SQL queries:
> https://issues.apache.org/
>> jira/browse/IGNITE-4510,
>>   https://issues.apache.org/jira/browse/IGNITE-4509
>>-
>> 
>> 3. .NET:
>>- Peer-class loading: https://issues.apache.org/
>> jira/browse/IGNITE-2492
>>- SQLDependency: https://issues.apache.org/
>>> jira/browse/IGNITE-2657
>> 
>> 4. C++:
>>- Compute Grid: https://issues.apache.org/
>>> jira/browse/IGNITE-3574
>> 
>> 5. ML Grid:
>>- Linear regression algorithms: https://issues.apache.org/
>> jira/browse/IGNITE-5012
>>- K-means clustering: https://issues.apache.org/
>> jira/browse/IGNITE-5113
>> 
>> 
>> Please join the thread and share your thoughts, ideas and concerns.
>> 
>> —
>> Denis
>> 
>> 
>> 
> 
> 
> 
> 
> --
> Best Regards, Vyacheslav
> 
 
>>> 
>>> 
>>> 
>>> --
>>> Best Regards, Vyacheslav
>>> 
>> 

[GitHub] ignite pull request #1946: Ignite 5131

[iveselovskiy]

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 these changes as the patch at:

https://github.com/apache/ignite/pull/1946.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1946


commit bfb00b6e61f9709718c30971997aeb0ac79e86b4
Author: Alexandr Kuramshin 
Date:   2016-11-18T20:12:28Z

IgniteTcpCommunicationBigClusterTest added

commit 02dd92e605b9b53f5a16c7ec5f8e7b5698b15ba4
Author: Alexandr Kuramshin 
Date:   2016-11-18T21:55:37Z

IgniteTcpCommunicationBigClusterTest update

commit 6acf193a3d356d1bad4c02a53ac76833ed1008d0
Author: Alexandr Kuramshin 
Date:   2016-11-19T09:55:45Z

Have got TcpCommunicationSpi error

commit 4fd39653d24f62f19f70b4dffba8497185cc46fb
Author: Alexandr Kuramshin 
Date:   2016-11-19T16:39:10Z

Some discovery have been done

commit c2c181922c7c24ea457577e32d2af897c8bec87f
Author: Alexandr Kuramshin 
Date:   2016-11-19T20:11:28Z

Prove that problem is not in the onFirstMessage hang

commit f8076edba097f6077229b2090ee3ff1a3369878c
Author: Alexandr Kuramshin 
Date:   2016-11-19T20:26:37Z

Revert: Prove that problem is not in the onFirstMessage hang

commit 6e1f2dfc2acb3dbb8f24aa51ed67b2ee447b4585
Author: Alexandr Kuramshin 
Date:   2016-11-21T08:55:09Z

Revert: pushing unnecessary changes to the master

commit ed794ca815f6bb1471af15779279d287576b39cc
Author: Alexandr Kuramshin 
Date:   2016-11-21T09:08:00Z

Revert: pushing unnecessary changes to the master

commit 3a57d63668bed239e21eca588134272783472e97
Author: iveselovskiy 
Date:   2016-12-09T14:13:37Z

Merge branch 'master' of https://github.com/apache/ignite

commit 166ad21d560c41c42a6de81cf5910537baa3ac92
Author: iveselovskiy 
Date:   2016-12-12T18:46:44Z

Merge branch 'master' of https://github.com/apache/ignite

commit 1eaba3e91bfe54c2bf6f761ac3f238a3b181a8e0
Author: iveselovskiy 
Date:   2017-03-27T18:41:07Z

Merge branch 'master' of https://github.com/apache/ignite

commit cef7775c9dcfc32b11a4cc4678b3a69a1e1b17da
Author: iveselovskiy 
Date:   2017-03-30T13:05:23Z

Merge branch 'master' of https://github.com/apache/ignite

commit 84e26d6fa2f6aec742fafb4d8145fbc9f697da70
Author: iveselovskiy 
Date:   2017-03-31T09:35:07Z

Merge branch 'master' of https://github.com/apache/ignite

commit be360213d74c9f005e4e3a1beb661323262bb7fb
Author: iveselovskiy 
Date:   2017-03-31T12:18:43Z

Merge branch 'master' of https://github.com/apache/ignite

commit ec3de454894f4bba4497b6c0ca0564a730525244
Author: iveselovskiy 
Date:   2017-04-17T15:22:00Z

Merge branch 'master' of https://github.com/apache/ignite

commit 88de0693b76c80fdc6533a799e0475fd53a4b0fc
Author: iveselovskiy 
Date:   2017-05-02T13:20:47Z

Merge branch 'master' of https://github.com/apache/ignite

commit 04d8f4ef69ea92b96642ecc3b797703858574c69
Author: iveselovskiy 
Date:   2017-05-11T13:23:05Z

Merge branch 'master' of https://github.com/apache/ignite

commit a4f3655a11f2b57c190d72588694ca036f10b898
Author: iveselovskiy 
Date:   2017-05-15T14:43:13Z

Merge branch 'master' of https://github.com/apache/ignite

commit a67c15db148735d01ef4d4227d80551224f548ff
Author: iveselovskiy 
Date:   2017-05-15T15:20:40Z

Merge branch 'master' of https://github.com/apache/ignite

commit 44afa7bea22ebb4a4ff33739122c16736c434de3
Author: iveselovskiy 
Date:   2017-05-15T17:30:44Z

IGNITE-5131: changed version of asm-all lib in hadoop module .




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[rfqu]

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 https://github.com/rfqu/ignite ignite-4831

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1945.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1945


commit 8123b84a9b7d5322455dc67187b2d2f6673f61ab
Author: rfqu 
Date:   2017-05-15T16:19:32Z

IGNITE-4831 fixed (Add an option to disable MBeans). Option 
IGNITE_DISABLE_MBEANS added.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[rfqu]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[rfqu]

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 https://github.com/rfqu/ignite ignite-4831

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1944.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1944


commit 8123b84a9b7d5322455dc67187b2d2f6673f61ab
Author: rfqu 
Date:   2017-05-15T16:19:32Z

IGNITE-4831 fixed (Add an option to disable MBeans). Option 
IGNITE_DISABLE_MBEANS added.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Data compression in Ignite 2.0

[Vyacheslav Daradur]

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 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: 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 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
> won't
> > > be compressed, only serialized values of an object fields (in bytes
> array
> > > form) will be compressed.
> > >
> > > This solution have some contentious issues:
> > > - small values, like primitives and short arrays - there isn't sense to
> > > compress them;
> > > - there is no possible to use compression with java-predefined types;
> > >
> > > We can provide an annotation, @IgniteCompression - for example, which
> can
> > > be used by users for marking fields to compress.
> > >
> > > Any thoughts?
> > >
> > > Maybe someone already have ready design?
> > >
> > > 2017-04-10 11:06 GMT+03:00 Vyacheslav Daradur :
> > >
> > >> Alexey,
> > >>
> > >> Yes, I've read it.
> > >>
> > >> Ok, let's discuss about public API design.
> > >>
> > >> I think we need to add some a configure entity to CacheConfiguration,
> > >> which will contain the Compressor interface implementation and some
> > usefull
> > >> parameters.
> > >> Or maybe to provide a BinaryMarshaller decorator, which will be
> compress
> > >> data after marshalling.
> > >>
> > >>
> > >> 2017-04-10 10:40 GMT+03:00 Alexey Kuznetsov :
> > >>
> > >>> Vyacheslav,
> > >>>
> > >>> Did you read initial discussion [1] about compression?
> > >>> As far as I remember we agreed to add only some "top-level" API in
> > order
> > >>> to
> > >>> provide a way for
> > >>> Ignite users to inject some sort of custom compression.
> > >>>
> > >>>
> > >>> [1]
> > >>> http://apache-ignite-developers.2346864.n4.nabble.com/Data-c
> > >>> ompression-in-Ignite-2-0-td10099.html
> > >>>
> > >>> On Mon, Apr 10, 2017 at 2:19 PM, daradurvs 
> > wrote:
> > >>>
> > >>> > Hi Igniters!
> > >>> >
> > >>> > I am interested in this task.
> > >>> > Provide some kind of pluggable compression SPI support
> > >>> > 
> > >>> >
> > >>> > I developed a solution on BinaryMarshaller-level, but reviewer has
> > >>> rejected
> > >>> > it.
> > >>> >
> > >>> > Let's continue discussion of task goals and solution design.
> > >>> > As I understood that, the main goal of this task is to store data
> in
> > >>> > compressed form.
> > >>> > This is what I need from Ignite as its user. Compression provides
> > >>> economy
> > >>> > on
> > >>> > servers.
> > >>> > We can store more data on same servers at the cost of increasing
> CPU
> > >>> > utilization.
> > >>> >
> > >>> > I'm researching a possibility of implementation of compression at
> the
> > >>> > cache-level.
> > >>> >
> > >>> > Any thoughts?
> > >>> >
> > >>> > --
> > >>> > Best regards,
> > >>> > Vyacheslav
> > >>> >
> > >>> >
> > >>> >
> > >>> >
> > >>> > --
> > >>> > View this message in context: http://apache-ignite-
> > >>> > developers.2346864.n4.nabble.com/Data-compression-in-
> > >>> > Ignite-2-0-tp10099p16317.html
> > >>> > Sent from the Apache Ignite Developers mailing list archive at
> > >>> Nabble.com.
> > >>> >
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Alexey Kuznetsov
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> Best Regards, Vyacheslav
> > >>
> > >
> > >
> > >
> > > --
> > > Best Regards, Vyacheslav
> > >
> >
> >
> >
> > --
> > Best Regards, Vyacheslav
> >
>



-- 
Best Regards, Vyacheslav

Re: Data compression in Ignite 2.0

[Dmitriy Setrakyan]

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: 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 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 won't
> > be compressed, only serialized values of an object fields (in bytes array
> > form) will be compressed.
> >
> > This solution have some contentious issues:
> > - small values, like primitives and short arrays - there isn't sense to
> > compress them;
> > - there is no possible to use compression with java-predefined types;
> >
> > We can provide an annotation, @IgniteCompression - for example, which can
> > be used by users for marking fields to compress.
> >
> > Any thoughts?
> >
> > Maybe someone already have ready design?
> >
> > 2017-04-10 11:06 GMT+03:00 Vyacheslav Daradur :
> >
> >> Alexey,
> >>
> >> Yes, I've read it.
> >>
> >> Ok, let's discuss about public API design.
> >>
> >> I think we need to add some a configure entity to CacheConfiguration,
> >> which will contain the Compressor interface implementation and some
> usefull
> >> parameters.
> >> Or maybe to provide a BinaryMarshaller decorator, which will be compress
> >> data after marshalling.
> >>
> >>
> >> 2017-04-10 10:40 GMT+03:00 Alexey Kuznetsov :
> >>
> >>> Vyacheslav,
> >>>
> >>> Did you read initial discussion [1] about compression?
> >>> As far as I remember we agreed to add only some "top-level" API in
> order
> >>> to
> >>> provide a way for
> >>> Ignite users to inject some sort of custom compression.
> >>>
> >>>
> >>> [1]
> >>> http://apache-ignite-developers.2346864.n4.nabble.com/Data-c
> >>> ompression-in-Ignite-2-0-td10099.html
> >>>
> >>> On Mon, Apr 10, 2017 at 2:19 PM, daradurvs 
> wrote:
> >>>
> >>> > Hi Igniters!
> >>> >
> >>> > I am interested in this task.
> >>> > Provide some kind of pluggable compression SPI support
> >>> > 
> >>> >
> >>> > I developed a solution on BinaryMarshaller-level, but reviewer has
> >>> rejected
> >>> > it.
> >>> >
> >>> > Let's continue discussion of task goals and solution design.
> >>> > As I understood that, the main goal of this task is to store data in
> >>> > compressed form.
> >>> > This is what I need from Ignite as its user. Compression provides
> >>> economy
> >>> > on
> >>> > servers.
> >>> > We can store more data on same servers at the cost of increasing CPU
> >>> > utilization.
> >>> >
> >>> > I'm researching a possibility of implementation of compression at the
> >>> > cache-level.
> >>> >
> >>> > Any thoughts?
> >>> >
> >>> > --
> >>> > Best regards,
> >>> > Vyacheslav
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > View this message in context: http://apache-ignite-
> >>> > developers.2346864.n4.nabble.com/Data-compression-in-
> >>> > Ignite-2-0-tp10099p16317.html
> >>> > Sent from the Apache Ignite Developers mailing list archive at
> >>> Nabble.com.
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Alexey Kuznetsov
> >>>
> >>
> >>
> >>
> >> --
> >> Best Regards, Vyacheslav
> >>
> >
> >
> >
> > --
> > Best Regards, Vyacheslav
> >
>
>
>
> --
> Best Regards, Vyacheslav
>

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

[dspavlov]

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 ignite-4938

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1943.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1943


commit faa8681ab35e2332a7b16210492468495eb9518e
Author: Alexander Paschenko 
Date:   2017-04-10T16:47:17Z

IGNITE-4938 De-pub of OptimizedMarshaller - take 1

commit a3686db055a55c87484ebad04e37f13ad06f93ce
Author: Alexander Paschenko 
Date:   2017-04-11T11:43:48Z

Merge branch 'master' into ignite-4938

commit 7942d585fde3fd11964f479b0442caa2ba0459d1
Author: Alexander Paschenko 
Date:   2017-04-11T16:10:37Z

IGNITE-4938 De-pub of OptimizedMarshaller - take 2

commit 1115ca5f81dc1a729cc16bcffd6ad5697b82e319
Author: Alexander Paschenko 
Date:   2017-04-12T00:44:42Z

IGNITE-4938 OptimizedMarshaller de-pub take 3 - removed redundant test 
suites

commit c89cc392f6e9f3008707a532422e10ba12fe44f1
Author: Alexey Goncharuk 
Date:   2017-04-14T15:00:51Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-4938

Conflicts:
examples/config/filesystem/example-igfs.xml
modules/clients/src/test/config/jdbc-config.xml
modules/core/src/main/java/org/apache/ignite/IgniteSystemProperties.java
modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java

modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryClassDescriptor.java

modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryContext.java

modules/core/src/main/java/org/apache/ignite/internal/client/marshaller/optimized/GridClientOptimizedMarshaller.java

modules/core/src/main/java/org/apache/ignite/internal/client/marshaller/optimized/GridClientZipOptimizedMarshaller.java

modules/core/src/main/java/org/apache/ignite/internal/marshaller/optimized/OptimizedClassDescriptor.java

modules/core/src/main/java/org/apache/ignite/internal/marshaller/optimized/OptimizedMarshaller.java

modules/core/src/main/java/org/apache/ignite/internal/marshaller/optimized/package-info.java
modules/core/src/main/java/org/apache/ignite/marshaller/Marshaller.java

modules/core/src/main/java/org/apache/ignite/marshaller/jdk/JdkMarshaller.java

modules/core/src/main/java/org/apache/ignite/marshaller/optimized/package-info.java
modules/core/src/main/resources/META-INF/classnames.properties
modules/core/src/test/config/example-cache.xml
modules/core/src/test/config/igfs-loopback.xml
modules/core/src/test/config/igfs-shmem.xml
modules/core/src/test/config/spring-start-nodes-attr.xml
modules/core/src/test/config/spring-start-nodes.xml
modules/core/src/test/config/websession/example-cache-base.xml

modules/core/src/test/java/org/apache/ignite/IgniteExternalizableAbstractTest.java

modules/core/src/test/java/org/apache/ignite/cache/store/jdbc/CacheJdbcPojoStoreOptimizedMarshallerSelfTest.java
modules/core/src/test/java/org/apache/ignite/igfs/IgfsPathSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/GridLifecycleAwareSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/managers/GridManagerStopSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/marshaller/optimized/package-info.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/CacheStartupInDeploymentModesTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/GridCacheEntryMemorySizeSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/GridCacheStoreManagerDeserializationTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/GridCacheVersionSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/CacheAffinityEarlyTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/CacheGetFutureHangsSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/IgniteCacheCreatePutMultiNodeSelfTest.java

modules/core/src/test/java/org/apache/ignite/internal/processors/cache/distributed/IgniteCacheCreatePutTest.java

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

[dspavlov]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[AMashenkov]

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

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1942.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1942


commit 66cef22366a8129f54a4839792a4b24e8014c00c
Author: Andrey V. Mashenkov 
Date:   2017-05-15T14:39:52Z

IGNITE-5225: Fixed thread pools incorrect shutdown.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[rishi007bansod]

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
  

I want to store data in multiple caches(with different cache names) in
Apache Ignite from Python either using redis client or using memcache
client. How can I do this? Also, are SQL queries supported when we use
Memcached or redis client for caching data in Ignite from Python.



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Store-data-from-Python-in-multiple-caches-using-Redis-or-Memcached-client-in-Apache-ignite-tp17660.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

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

[dspavlov]

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 ignite-2.0

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1941.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1941


commit d8480bdc22048ffadd3716f5d3a1f1c6a1797a0f
Author: devozerov 
Date:   2017-04-18T12:24:19Z

IGNITE-4990: Removed deprecated properties from FileSystemConfiguration. 
This closes #1816.

commit eaf7350c64aabd98084df4eca337923c0208d085
Author: devozerov 
Date:   2017-04-18T12:25:27Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 3565e4ee60e705e0bc34a73045a8b9b161df2e6e
Author: Anton Vinogradov 
Date:   2017-04-18T12:32:29Z

Special profiles to set versions and check compilation across all modules

commit 862d8af0a27974eec76665a8d336a4be4c08361a
Author: Dmitriy Govorukhin 
Date:   2017-04-18T12:42:54Z

master - fixed SPI test

commit c4d81808c3cc002f1c71afb275361b728a84440b
Author: Dmitriy Govorukhin 
Date:   2017-04-18T12:44:15Z

master - Fixed jetty REST processor testIncorrectPut

commit 22580e19b7ae5d11b8c299e2b3d92f5c8b9f0e8c
Author: Alexander Belyak 
Date:   2017-04-18T11:56:50Z

IGNITE-4927 Write behind - add an option to skip write coalescing

Signed-off-by: nikolay_tikhonov 

commit 58a8cb2579665c989ea9b08ebebf7b050f4d1405
Author: Pavel Tupitsyn 
Date:   2017-04-18T13:01:49Z

.NET: Fix MessagingTest flakiness

commit 7038af4a7d976e59a7875b32b3ee3dfc1758908d
Author: Yury Babak 
Date:   2017-04-18T13:46:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation

commit d78e071a7de1129838652e9f377ff73d3a84495d
Author: Yury Babak 
Date:   2017-04-18T13:47:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation

commit d60cf53bbfae162ac96ec1525bcd1772b8249a79
Author: Konstantin Dudkov 
Date:   2017-04-18T13:50:16Z

ignite-4982 Fixed GridIntList.

commit 43d6d7e7eb9eb146c48b843293849ac687ead216
Author: sboikov 
Date:   2017-04-18T13:50:45Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 8ea9f83ce7f21f6ba50c0c644f62319f25b56ebd
Author: Alexey Kuznetsov 
Date:   2017-04-18T13:39:58Z

master Fixed Visor tests.
(cherry picked from commit 36a6cd0)

commit 735ce60da02ebadc43aaa29cc97d331b8056df36
Author: Valentin Kulichenko 
Date:   2017-04-13T08:29:30Z

IGNITE-4954 - Configurable expiration timeout for Cassandra session. This 
closes #1785.

commit 9e7421f261354b28119094b3b53b9490fd817b24
Author: devozerov 
Date:   2017-04-18T14:04:43Z

Merge branch 'master' into ignite-2.0

commit 2edb935cbf87198993c403724e26efc655710c25
Author: devozerov 
Date:   2017-04-18T14:11:34Z

IGNITE-4565: Implemented CREATE INDEX and DROP INDEX. This closes #1773. 
This closes #1804.

commit 9b21c85d6ec0cdbba8cbf2382559a8ef5a82e15c
Author: Alexey Goncharuk 
Date:   2017-04-18T15:40:27Z

master - Mute test with a correct link

commit f82ed01807c80b36b7e361a5800ea131c1431c14
Author: Alexey Goncharuk 
Date:   2017-04-18T15:40:55Z

master - Fix mvcc tests after CLOCK mode removal

commit 36e7e19830dc53c0ed02a0d83806b2cb5a7c7ce5
Author: Alexey Kuznetsov 
Date:   2017-04-19T04:34:16Z

IGNITE-4988 Cleanup code.

commit d38348432a2b8b66999c6410ec4f5c1ef050191d
Author: sboikov 
Date:   2017-04-19T09:46:31Z

Attempt to fix awaitPartitionMapExchange: wait for last exchange completion 
to avoid races with cache destroy.

commit 22d5e55bee69403c4f9f8da9c113751ce110aa2d
Author: tledkov-gridgain 
Date:   2017-04-19T09:54:14Z

IGNITE-3523 IGFS: Remove "initialize default path modes" feature. This 
closes #1786.

commit 2ded758ad1f1663aea05ca943ecf509b1574c0bf
Author: devozerov 
Date:   2017-04-19T09:54:34Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 800b8bd90033ab64f4299ba242cc89b1f4c98417
Author: Alexey Goncharuk 
Date:   2017-04-19T10:55:02Z

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

[dspavlov]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5227:


 Summary: StackOverflowError in 
GridCacheMapEntry#checkOwnerChanged()
 Key: IGNITE-5227
 URL: https://issues.apache.org/jira/browse/IGNITE-5227
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.6
Reporter: Alexey Goncharuk
Priority: Critical
 Fix For: 2.1


A simple test reproducing this error:
{code}
/**
 * @throws Exception if failed.
 */
public void testBatchUnlock() throws Exception {
startGrid(0);

try {
final CountDownLatch releaseLatch = new CountDownLatch(1);

IgniteInternalFuture fut = GridTestUtils.runAsync(new 
Callable() {
@Override public Object call() throws Exception {
IgniteCache cache = grid(0).cache(null);

Lock lock = cache.lock("key");

try {
lock.lock();

releaseLatch.await();
}
finally {
lock.unlock();
}

return null;
}
});

Map putMap = new LinkedHashMap<>();

putMap.put("key", "trigger");

for (int i = 0; i < 10_000; i++)
putMap.put("key-" + i, "value");

IgniteCache asyncCache = 
grid(0).cache(null).withAsync();

asyncCache.putAll(putMap);

IgniteFuture resFut = asyncCache.future();

Thread.sleep(1000);

releaseLatch.countDown();

fut.get();

resFut.get();
}
finally {
stopAllGrids();
}
{code}
We should replace a recursive call with a simple iteration over the linked list.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[dspavlov]

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 these changes as the patch at:

https://github.com/apache/ignite/pull/1940.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1940


commit d8480bdc22048ffadd3716f5d3a1f1c6a1797a0f
Author: devozerov 
Date:   2017-04-18T12:24:19Z

IGNITE-4990: Removed deprecated properties from FileSystemConfiguration. 
This closes #1816.

commit eaf7350c64aabd98084df4eca337923c0208d085
Author: devozerov 
Date:   2017-04-18T12:25:27Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 3565e4ee60e705e0bc34a73045a8b9b161df2e6e
Author: Anton Vinogradov 
Date:   2017-04-18T12:32:29Z

Special profiles to set versions and check compilation across all modules

commit 862d8af0a27974eec76665a8d336a4be4c08361a
Author: Dmitriy Govorukhin 
Date:   2017-04-18T12:42:54Z

master - fixed SPI test

commit c4d81808c3cc002f1c71afb275361b728a84440b
Author: Dmitriy Govorukhin 
Date:   2017-04-18T12:44:15Z

master - Fixed jetty REST processor testIncorrectPut

commit 22580e19b7ae5d11b8c299e2b3d92f5c8b9f0e8c
Author: Alexander Belyak 
Date:   2017-04-18T11:56:50Z

IGNITE-4927 Write behind - add an option to skip write coalescing

Signed-off-by: nikolay_tikhonov 

commit 58a8cb2579665c989ea9b08ebebf7b050f4d1405
Author: Pavel Tupitsyn 
Date:   2017-04-18T13:01:49Z

.NET: Fix MessagingTest flakiness

commit 7038af4a7d976e59a7875b32b3ee3dfc1758908d
Author: Yury Babak 
Date:   2017-04-18T13:46:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation

commit d78e071a7de1129838652e9f377ff73d3a84495d
Author: Yury Babak 
Date:   2017-04-18T13:47:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation

commit d60cf53bbfae162ac96ec1525bcd1772b8249a79
Author: Konstantin Dudkov 
Date:   2017-04-18T13:50:16Z

ignite-4982 Fixed GridIntList.

commit 43d6d7e7eb9eb146c48b843293849ac687ead216
Author: sboikov 
Date:   2017-04-18T13:50:45Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 8ea9f83ce7f21f6ba50c0c644f62319f25b56ebd
Author: Alexey Kuznetsov 
Date:   2017-04-18T13:39:58Z

master Fixed Visor tests.
(cherry picked from commit 36a6cd0)

commit 735ce60da02ebadc43aaa29cc97d331b8056df36
Author: Valentin Kulichenko 
Date:   2017-04-13T08:29:30Z

IGNITE-4954 - Configurable expiration timeout for Cassandra session. This 
closes #1785.

commit 9e7421f261354b28119094b3b53b9490fd817b24
Author: devozerov 
Date:   2017-04-18T14:04:43Z

Merge branch 'master' into ignite-2.0

commit 2edb935cbf87198993c403724e26efc655710c25
Author: devozerov 
Date:   2017-04-18T14:11:34Z

IGNITE-4565: Implemented CREATE INDEX and DROP INDEX. This closes #1773. 
This closes #1804.

commit 66a7eb3c6bd77d4af1a04f2224feac5c1a7e9fcb
Author: Sergi Vladykin 
Date:   2017-04-18T14:21:20Z

master - test adjusted

commit 5d8e31806ac8c013169c9892c0f88b79d6833358
Author: Anton Vinogradov 
Date:   2017-04-18T12:32:29Z

Special profiles to set versions and check compilation across all modules
(cherry picked from commit 3565e4e)

commit 0abf6601fc1ff1e6e659381666ae706e31b51de0
Author: Yury Babak 
Date:   2017-04-18T13:47:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation
(cherry picked from commit d78e071)

commit 364c38661a1864e0b823be737998ed66927d11ca
Author: Alexey Goncharuk 
Date:   2017-04-18T15:40:27Z

master - Mute test with a correct link

commit 0da51d4110ab13f42f0ee5a2fc3181fc50656cd4
Author: Alexey Goncharuk 
Date:   2017-04-18T15:40:55Z

master - Fix mvcc tests after CLOCK mode removal

commit 9b21c85d6ec0cdbba8cbf2382559a8ef5a82e15c
Author: Alexey Goncharuk 
Date:   2017-04-18T15:40:27Z

master - Mute test with a correct link

commit f82ed01807c80b36b7e361a5800ea131c1431c14
Author: Alexey Goncharuk 

Re: Data compression in Ignite 2.0

[Vyacheslav Daradur]

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 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 won't
> be compressed, only serialized values of an object fields (in bytes array
> form) will be compressed.
>
> This solution have some contentious issues:
> - small values, like primitives and short arrays - there isn't sense to
> compress them;
> - there is no possible to use compression with java-predefined types;
>
> We can provide an annotation, @IgniteCompression - for example, which can
> be used by users for marking fields to compress.
>
> Any thoughts?
>
> Maybe someone already have ready design?
>
> 2017-04-10 11:06 GMT+03:00 Vyacheslav Daradur :
>
>> Alexey,
>>
>> Yes, I've read it.
>>
>> Ok, let's discuss about public API design.
>>
>> I think we need to add some a configure entity to CacheConfiguration,
>> which will contain the Compressor interface implementation and some usefull
>> parameters.
>> Or maybe to provide a BinaryMarshaller decorator, which will be compress
>> data after marshalling.
>>
>>
>> 2017-04-10 10:40 GMT+03:00 Alexey Kuznetsov :
>>
>>> Vyacheslav,
>>>
>>> Did you read initial discussion [1] about compression?
>>> As far as I remember we agreed to add only some "top-level" API in order
>>> to
>>> provide a way for
>>> Ignite users to inject some sort of custom compression.
>>>
>>>
>>> [1]
>>> http://apache-ignite-developers.2346864.n4.nabble.com/Data-c
>>> ompression-in-Ignite-2-0-td10099.html
>>>
>>> On Mon, Apr 10, 2017 at 2:19 PM, daradurvs  wrote:
>>>
>>> > Hi Igniters!
>>> >
>>> > I am interested in this task.
>>> > Provide some kind of pluggable compression SPI support
>>> > 
>>> >
>>> > I developed a solution on BinaryMarshaller-level, but reviewer has
>>> rejected
>>> > it.
>>> >
>>> > Let's continue discussion of task goals and solution design.
>>> > As I understood that, the main goal of this task is to store data in
>>> > compressed form.
>>> > This is what I need from Ignite as its user. Compression provides
>>> economy
>>> > on
>>> > servers.
>>> > We can store more data on same servers at the cost of increasing CPU
>>> > utilization.
>>> >
>>> > I'm researching a possibility of implementation of compression at the
>>> > cache-level.
>>> >
>>> > Any thoughts?
>>> >
>>> > --
>>> > Best regards,
>>> > Vyacheslav
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > View this message in context: http://apache-ignite-
>>> > developers.2346864.n4.nabble.com/Data-compression-in-
>>> > Ignite-2-0-tp10099p16317.html
>>> > Sent from the Apache Ignite Developers mailing list archive at
>>> Nabble.com.
>>> >
>>>
>>>
>>>
>>> --
>>> Alexey Kuznetsov
>>>
>>
>>
>>
>> --
>> Best Regards, Vyacheslav
>>
>
>
>
> --
> Best Regards, Vyacheslav
>



-- 
Best Regards, Vyacheslav

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

[Vyacheslav Daradur (JIRA)]

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 Feature
  Components: binary, cache
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur
 Fix For: 2.1


Develop solution for compression of annotated fields of an object.

For example:
{code}
class Foo {
@BinaryCompession
String data;
}
{code}

It must be compatible with querying and indexing.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[dkarachentsev]

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 https://github.com/gridgain/apache-ignite ignite-5223

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1939.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1939






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[Yury Babak]

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,  IGNITE-5218
  .
* Generalization of cost function for Linear Regression,  IGNITE-5219
  .
* Investigate possibility of integrating with dl4j,  IGNITE-5221
  .

Regards,
Yury Babak. 



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-ML-next-steps-IGNITE-5029-tp17096p17651.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

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

[Dmitry Karachentsev (JIRA)]

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
  Issue Type: Bug
Affects Versions: 1.9
Reporter: Dmitry Karachentsev
Assignee: Dmitry Karachentsev
 Fix For: 1.9


Add system property that will use local binary metadata cache instead of 
distributed one, when all classes available on all nodes and don't change.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Pavel Tupitsyn (JIRA)]

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: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.1


Add {{String.PadLeft}} and {{String.PadRight}} functions to LINQ, map them to 
SQL {{LPAD}} and {{RPAD}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[glukos]

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 ignite-5215

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1938.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1938


commit 6319266003704b4bc478de9ba0af6b4c5f84af9a
Author: Ivan Rakov 
Date:   2017-05-15T12:27:00Z

IGNITE-5215: Allow user to configure memory policy with maxSize lesser than 
default initialSize




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[Pavel Tupitsyn (JIRA)]

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
  Issue Type: Bug
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.1


This works:
{{orgs.AsCacheQueryable().Select(x => x.Value.Name.IndexOf("a")).Dump();}}

This does not:
{{orgs.AsCacheQueryable().Select(x => x.Value.Name.IndexOf('a')).Dump();}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Yury Babak (JIRA)]

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
  Components: ml
Reporter: Yury Babak


We need mechanism of computation of partial derivatives which we need for 
gradient descent.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Vyacheslav Daradur]

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 
> ci.tests 
> PR 
>
>
> --
> Best Regards, Vyacheslav
>



-- 
Best Regards, Vyacheslav

Re: Data compression in Ignite 2.0

[Vyacheslav Daradur]

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 won't be
compressed, only serialized values of an object fields (in bytes array
form) will be compressed.

This solution have some contentious issues:
- small values, like primitives and short arrays - there isn't sense to
compress them;
- there is no possible to use compression with java-predefined types;

We can provide an annotation, @IgniteCompression - for example, which can
be used by users for marking fields to compress.

Any thoughts?

Maybe someone already have ready design?

2017-04-10 11:06 GMT+03:00 Vyacheslav Daradur :

> Alexey,
>
> Yes, I've read it.
>
> Ok, let's discuss about public API design.
>
> I think we need to add some a configure entity to CacheConfiguration,
> which will contain the Compressor interface implementation and some usefull
> parameters.
> Or maybe to provide a BinaryMarshaller decorator, which will be compress
> data after marshalling.
>
>
> 2017-04-10 10:40 GMT+03:00 Alexey Kuznetsov :
>
>> Vyacheslav,
>>
>> Did you read initial discussion [1] about compression?
>> As far as I remember we agreed to add only some "top-level" API in order
>> to
>> provide a way for
>> Ignite users to inject some sort of custom compression.
>>
>>
>> [1]
>> http://apache-ignite-developers.2346864.n4.nabble.com/Data-
>> compression-in-Ignite-2-0-td10099.html
>>
>> On Mon, Apr 10, 2017 at 2:19 PM, daradurvs  wrote:
>>
>> > Hi Igniters!
>> >
>> > I am interested in this task.
>> > Provide some kind of pluggable compression SPI support
>> > 
>> >
>> > I developed a solution on BinaryMarshaller-level, but reviewer has
>> rejected
>> > it.
>> >
>> > Let's continue discussion of task goals and solution design.
>> > As I understood that, the main goal of this task is to store data in
>> > compressed form.
>> > This is what I need from Ignite as its user. Compression provides
>> economy
>> > on
>> > servers.
>> > We can store more data on same servers at the cost of increasing CPU
>> > utilization.
>> >
>> > I'm researching a possibility of implementation of compression at the
>> > cache-level.
>> >
>> > Any thoughts?
>> >
>> > --
>> > Best regards,
>> > Vyacheslav
>> >
>> >
>> >
>> >
>> > --
>> > View this message in context: http://apache-ignite-
>> > developers.2346864.n4.nabble.com/Data-compression-in-
>> > Ignite-2-0-tp10099p16317.html
>> > Sent from the Apache Ignite Developers mailing list archive at
>> Nabble.com.
>> >
>>
>>
>>
>> --
>> Alexey Kuznetsov
>>
>
>
>
> --
> Best Regards, Vyacheslav
>



-- 
Best Regards, Vyacheslav

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

[Yury Babak (JIRA)]

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
Reporter: Yury Babak


We want to implement Decision trees for Ignite ML because it's really common 
one for ML.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Yury Babak (JIRA)]

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
Reporter: Yury Babak


We should implement Gradient Descent for Ignite ML. Current we have only normal 
equation for linear regression.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Yury Babak (JIRA)]

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
  Components: ml
Reporter: Yury Babak


We want to add Stream API support to Ignite matrices and possibly to vectors. 
We already have implementation of Spliterator for AbstractVector and 
AbstractMatrix so it's looks like next step.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Ivan Rakov (JIRA)]

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
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.0
Reporter: Ivan Rakov
Assignee: Ivan Rakov


Attempt to create memory policy with small maxSize ends with error:
{noformat}
Caused by: class org.apache.ignite.IgniteCheckedException: MemoryPolicy maxSize 
must not be smaller than initialSize [name=dfltMemPlc, initSize=268,4 MB, 
maxSize=209,7 MB]
at 
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.checkPolicySize(IgniteCacheDatabaseSharedManager.java:419)
at 
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.validateConfiguration(IgniteCacheDatabaseSharedManager.java:337)
at 
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.init(IgniteCacheDatabaseSharedManager.java:112)
at 
org.apache.ignite.internal.processors.cache.database.IgniteCacheDatabaseSharedManager.start0(IgniteCacheDatabaseSharedManager.java:99)
at 
org.gridgain.grid.internal.processors.cache.database.GridCacheDatabaseSharedManager.initDataBase(GridCacheDatabaseSharedManager.java:493)
at 
org.gridgain.grid.internal.processors.cache.database.GridCacheDatabaseSharedManager.start0(GridCacheDatabaseSharedManager.java:436)
at 
org.apache.ignite.internal.processors.cache.GridCacheSharedManagerAdapter.start(GridCacheSharedManagerAdapter.java:53)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.start(GridCacheProcessor.java:644)
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1763)
... 29 more
{noformat}
This can be easily fixed by setting initialSize. Though, it would be better to 
don't oblige user spending time on fixing it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[ptupitsyn]

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 review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1937.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1937


commit 44f3d90e4e162460754ba4e7d2158ca25d0dbec1
Author: Pavel Tupitsyn 
Date:   2017-01-11T14:12:50Z

Adding tests

commit 60772b69cc059326b873aee8866dbf74aedeb1b1
Author: Pavel Tupitsyn 
Date:   2017-01-11T15:42:12Z

wip tests

commit f099a22bd2632cf3da2fb537fdffc533e46c25de
Author: Pavel Tupitsyn 
Date:   2017-01-11T16:18:21Z

wip tests

commit f4e036c9211c99c98a51ccafa6ff86eaec9391b4
Author: Pavel Tupitsyn 
Date:   2017-01-11T16:18:44Z

wip

commit 5ac39038ec816f81cdd960745d39fdc6d08c8efc
Author: Pavel Tupitsyn 
Date:   2017-01-11T16:29:52Z

wip tests

commit 3fdd04c0adfc13d3be1ab1066bf5f85efde5769d
Author: Pavel Tupitsyn 
Date:   2017-01-11T16:30:05Z

wip

commit 4792aa1bbb1b2440f340748f2a56f3954d34eb8b
Author: Pavel Tupitsyn 
Date:   2017-01-11T16:38:14Z

wip

commit fe20574763b494c82bd6672ac7538de4083b6d8d
Author: Pavel Tupitsyn 
Date:   2017-01-12T12:08:30Z

wip tests

commit 58a8ff78e8b8eb1d22c19cc5d6d6e8f55a07d325
Author: Pavel Tupitsyn 
Date:   2017-01-12T12:12:21Z

Test done

commit 0e371fbc9787625376d41921fb07e9d7aa2ddc74
Author: Pavel Tupitsyn 
Date:   2017-01-12T12:28:44Z

Remove current assembly resolver

commit 726ed99a4e00d6e5494e2f8abacf810483be2a94
Author: Pavel Tupitsyn 
Date:   2017-01-12T12:50:06Z

wip

commit 224f6465a6b1bb8c272fda56ecf1265ecd379388
Author: Pavel Tupitsyn 
Date:   2017-01-12T13:16:01Z

Refactor LoadedAssembliesResolver usage to SerializableObjectHolder

commit 884246e39b798e9137a1d5d6cf166babe9395fa9
Author: Pavel Tupitsyn 
Date:   2017-01-12T13:39:11Z

IsPeerAssemblyLoadingEnabled

commit cda5f9e01430f49e5961515e8fb0e6db51de0a92
Author: Pavel Tupitsyn 
Date:   2017-01-12T13:47:30Z

PeerAssemblyResolver added

commit 4ff92856a859ae8b32583a5861a46fdf02801991
Author: Pavel Tupitsyn 
Date:   2017-01-12T13:54:42Z

GetAssemblyFunc

commit f52526cc7daf6cb28e598c6e17facf18c611873f
Author: Pavel Tupitsyn 
Date:   2017-01-12T14:01:37Z

wip AssemblyLoader

commit a113edc6bd082b7bf2530b3e599244fb199b3b22
Author: Pavel Tupitsyn 
Date:   2017-01-12T14:08:44Z

wip

commit 65f5aedb212282d39355192d2d96829a9edee2cf
Author: Pavel Tupitsyn 
Date:   2017-01-12T15:19:14Z

wip

commit 068e64b84e1c2d39987ab4fdd1592db4cd55f58f
Author: Pavel Tupitsyn 
Date:   2017-01-12T15:24:10Z

wip

commit ffd896b19c8b3cca23b17944c3483b292bb73ce3
Author: Pavel Tupitsyn 
Date:   2017-01-12T15:43:00Z

wip tests

commit 75cbc6e12365c852e42652ec05a26b8b55a4fc50
Author: Pavel Tupitsyn 
Date:   2017-01-12T15:46:04Z

fix cluster

commit 1a004add3531f202fc5a82980dfbeaa879fbbf70
Author: Pavel Tupitsyn 
Date:   2017-01-12T16:02:14Z

Fix lazy instance

commit c66463a94f51df588addbc13069cd3f6f8473e6d
Author: Pavel Tupitsyn 
Date:   2017-01-12T16:18:33Z

Register system func

commit d103f134d9eee29a33fb23683b193ef48a775c29
Author: Pavel Tupitsyn 
Date:   2017-01-12T16:30:32Z

GetAssemblyByNameFunc

commit ea76139afe15543c07b2e1d24f41b00e72f74df9
Author: Pavel Tupitsyn 
Date:   2017-01-12T16:34:20Z

Test works for Serializable!

commit f75b2879919382d7316aa97113f7d48535b248b9
Author: Pavel Tupitsyn 
Date:   2017-01-12T16:41:17Z

binarizable test

commit 8f11f440dfa02bd3bb1dbee2892f3c79a7074216
Author: Pavel Tupitsyn 
Date:   2017-01-12T16:53:07Z

Fix binarizable test

commit fab4dca2715c2ba8d257e3729f08045dfe661f98
Author: Pavel Tupitsyn 
Date:   2017-01-13T07:48:05Z

Update config schema

commit 733aa0f5e96745286abac34305562000c73d90e2
Author: Pavel Tupitsyn 
Date:   2017-01-13T07:50:34Z

Update configuration tests

commit 6f3abd8271d15a86abcea871464f3fcaf4d1899a
Author: Pavel Tupitsyn 
Date:   2017-01-13T08:14:41Z

Cache assembly bytes in AssemblyLoader




---
If your project is set up for it, you 

[GitHub] ignite pull request #1934: Ignite 5112

[ybabak]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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!
>
> I want to update https://apacheignite.readme.io/docs/mesos-deployment
> with new text according with https://cwiki.apache.org/
> confluence/display/IGNITE/Documentation
> But have a problem with authentication, registered login
> vaopols...@gmail.com.
> Help me, please.
>
> New text:
>
> 3.Copy the following application definition (in JSON format) and save to
> marathon.json file. Update any parameters which would like to change.
>
>
>
> *A role name must be a valid directory name, so it cannot:  • Be an empty
> string  • Be . or ..  • Start with -  • Contain any slash, backspace, or
> whitespace character*
>  If doesn't set restriction on cluster then the framework will try to
> occupy all resources in Mesos cluster. See Configuration section below.
>
> JSON
> {
>   "id": "ignition",
>   "instances": 1,
>   "cpus": 2,
>   "mem": 2048,
>   "ports": [0],
>   "uris": [
> "http://host/ignite-mesos--jar-with-dependencies.jar"
>   ],
>   "env": {
> "IGNITE_NODE_COUNT": "4",
> "MESOS_MASTER_URL": "zk://localhost:2181/mesos",
> "IGNITE_RUN_CPU_PER_NODE": "2",
> "IGNITE_MEMORY_PER_NODE": "2048",
> "IGNITE_VERSION": "1.0.5",
>
>
> *"MESOS_USER" : "userA","MESOS_ROLE" :  "role1"*  },
>   "cmd": "java -jar ignite-mesos--
> jar-with-dependencies.jar"
> }
>
> Vadim
>
>
> 2017-04-27 19:29 GMT+03:00 Nikolay Tikhonov (JIRA) :
>
>>
>> [ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.
>> atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
>> l=15986959#comment-15986959 ]
>>
>> Nikolay Tikhonov commented on IGNITE-4052:
>> --
>>
>> [~javaller],
>> Thank you for your contribution. I've fixed some minors issue and pushed
>> your changes into {{ignite-4052}} branch. Please look at the changes.
>>
>> >I dont work with Mesos and think that anyone who has experience should
>> make it. OK?
>> I think that it good time to try it. ;) It looks strange when developer
>> don't run own code. [2] Also would be great to update docs [1]. Use for it
>> {{suggest edits}} button.
>>
>> 1. https://apacheignite.readme.io/docs/mesos-deployment
>> 2. http://mesos.apache.org/gettingstarted/
>>
>> > Add ability to set up users for MESOS
>> > -
>> >
>> > Key: IGNITE-4052
>> > URL: https://issues.apache.org/jira/browse/IGNITE-4052
>> > Project: Ignite
>> >  Issue Type: Improvement
>> >  Components: general
>> >Affects Versions: 1.7
>> >Reporter: Nikolay Tikhonov
>> >Assignee: Vadim Opolski
>> >Priority: Trivial
>> >
>> > In current implementation Ignite Mesos Framework connects to MESOS
>> cluster via current user. Need to add ability to configure this parameters
>> via system env properties. Also need to add properties for mesos role.
>> > See org/apache/ignite/mesos/IgniteFramework.java:537
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.15#6346)
>>
>
>

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

[AMashenkov]

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 review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1936.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1936


commit 39f678b252f7ea527fadf747cda4d64dafe2a38e
Author: Andrey V. Mashenkov 
Date:   2017-05-15T09:27:00Z

Fixed segmented indices snapshots.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[Nikolay Tikhonov (JIRA)]

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
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Nikolay Tikhonov
Assignee: Nikolay Tikhonov


ConcurrentModificationException with 
org.apache.ignite.continuous.query=DEBUG
{{noformat}}
Unexpected exception during cache update 
java.util.ConcurrentModificationException: null
at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1211)
at java.util.TreeMap$EntryIterator.next(TreeMap.java:1247)
at java.util.TreeMap$EntryIterator.next(TreeMap.java:1242)
at java.util.AbstractMap.toString(AbstractMap.java:554)
at java.lang.String.valueOf(String.java:2994)
at java.lang.StringBuilder.append(StringBuilder.java:131)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$PartitionRecovery.collectEntries(CacheContinuousQueryHandler.java:1132)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.handleEvent(CacheContinuousQueryHandler.java:739)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:792)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$800(CacheContinuousQueryHandler.java:91)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:419)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:347)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2669)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2390)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1792)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1632)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.mapSingle(GridNearAtomicAbstractUpdateFuture.java:263)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:494)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:436)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:208)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$23.apply(GridDhtAtomicCache.java:1152)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$23.apply(GridDhtAtomicCache.java:1150)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:847)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAsync0(GridDhtAtomicCache.java:1150)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putAsync0(GridDhtAtomicCache.java:619)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.putAsync(GridCacheAdapter.java:2574)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putIfAbsentAsync(GridDhtAtomicCache.java:664)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.putIfAbsent(GridDhtAtomicCache.java:657)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.putIfAbsent(IgniteCacheProxy.java:1451)
at 
com.workday.fabric.ignite.management.IgniteManagementService.doExecute(IgniteManagementService.java:174)
at 
com.workday.fabric.ignite.service.AbstractIgniteService.execute(AbstractIgniteService.java:94)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessor$3.run(GridServiceProcessor.java:1157)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 

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

[Pavel Tupitsyn (JIRA)]

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
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.1


See {{BinaryReflectiveActions:489}}. All types that implement {{IDictionary}} 
and are not generic are written as {{Hashtable}}, which is not correct, since 
type information is lost. Deserialization fails with {{InvalidCastException}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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