Off-Heap SQL Indexes

2016-11-02 Thread Prachi Garg 
Engineers,

I was going through documentation for Off-Heap SQL Indexes
 and
found two contradicting statements-

According to [1] -  " `CacheConfiguration.setOffHeapMaxMemory` is the only
property to enable or disable off-heap indexing. While
CacheConfiguration.setMemoryMode is used to configure off-heap memory
, it does not
have any effect on indexing."

According to [2] -  "Note that when off-heap memory is configured, Ignite
will store query indexes off-heap as well."


Which one is true?

[1] - https://apacheignite.readme.io/docs/sql-queries#off-heap-sql-indexes

[2] - http://apacheignite.gridgain.org/docs/off-heap-memory


Thanks,

-Prachi

Re: Talking to Ignite From PHP

2016-11-02 Thread Denis Magda 
Igor,

I can’t find branch ignite-3910. Most likely you keep the changes on the other 
one. Please double check.

In any case, I succeeded with some of the steps from the documentation and 
updated it making clearer.
http://apacheignite.gridgain.org/v1.7/docs/pdo-interoperability 


Please apply my latest notes related to the documentation.
https://issues.apache.org/jira/browse/IGNITE-3921 


Let me know as soon as the documentation is refined. I’ll keep at the 
installation and testing of PHP + Ignite scenario.

—
Denis

> On Nov 2, 2016, at 4:38 AM, Igor Sapego  wrote:
> 
> Denis,
> 
> I believe that you should switch to DML branch (ignite-2294),
> and then merge ignite-3910 into it.
> 
> That should be enough. Please let me know if there are any issues.
> 
> Best Regards,
> Igor
> 
> On Wed, Nov 2, 2016 at 3:12 AM, Denis Magda  > wrote:
> Igor,
> 
> I’m planning to prepare a blog post about our PHP + PDO + Ignite integration 
> and referring to the documentation template available for now
> https://apacheignite.readme.io/docs/pdo-interoperability 
> 
> 
> Considering that the fixes and improvements you did for Ignite ODBC driver in 
> order to support PDO have not been released yet what is a valid branch number 
> if I want to do the following:
> - connect to the cluster from PHP code.
> - populate a cache using DML INSERT command.
> - query the data with the usage of SQL.
> 
> —
> Denis
> 
>

Re: [DISCUSS] PMC Chair rotation time

2016-11-02 Thread Dmitriy Setrakyan 
While all the candidates suggested so far look good, I would propose Denis
Magda as the next PMC chair. His participation in the project does not only
have to do with the code, but also with Ignite project overall, including
website, documentation, new tickets, design, etc.

D.

On Wed, Nov 2, 2016 at 11:11 AM, Konstantin Boudnik  wrote:

> Just to reiterate the original premise for the rotation [1]:
> 
> - it provides an opportunity to anyone in the PMC to try this hat on and
> get
> more involved in the inner-workings of the ASF and see how the board
> operates
> - it guarantees that once you're a chair you aren't stuck holding the bag
> forever and can pass it on if your time allocation changes
> - such a policy makes the PMC very transparent
> 
>
> It ain't about supervision, as Chair doesn't have any magical powers over
> the
> PMC. It is mostly about helping the board to provide a better view into the
> project and be the representative of the board in the PMC. Most of the
> time it
> is boring, but once in a while it might require quite a bit of an ability
> to
> negotiate with people and be tasteful, if a situation gets sensitive for
> whatever reason. Being a Chair doesn't mean he or she will lead the
> technical
> side of the project: this responsibility comes as a consequence of one's
> merit,
> rather than an official title of a sort.
>
> [1] https://is.gd/bnVoaa
>
> Cheers,
>   Cos
>
> On Tue, Nov 01, 2016 at 02:31PM, Denis Magda wrote:
> > Fully support Cos’s proposal.
> >
> > It’s always a good intention to rotate positions like this even if
> > everything runs smooth under a supervision of the present chair.
> Moreover,
> > Dmitriy deserved some time to relax for the great job he did under this
> role :)
> >
> > From my side I would propose one more nominee - Valentin Kulichenko who
> > brings significant efforts spreading out the knowledge in and out of the
> > community, spends enormous amount of time assisting Ignite community and
> > contributes to the overall future of the project.
> >
> > As for my position, I’m not going to play mannerly games and would say
> that
> > I’m ready to take over this role if the community decides so. Why? This
> is a
> > matter of curiosity and abilities to make and learn more simply because
> > you’ll be responsible for something new.
> >
> > —
> > Denis
> >
> > > On Nov 1, 2016, at 8:00 AM, Sergi Vladykin 
> wrote:
> > >
> > > I'd say that the most proved candidate is Vladimir Putin :) But I want
> to
> > > nominate some more trusted guys to make sure that our election is true
> and
> > > representative:
> > >
> > > 1. I want to nominate Vladimir Ozerov, who plays a big role in our
> > > engineering efforts to make Apache Ignite successful.
> > >
> > > 2. Also I'd like to nominate Konstantin Boudnik who is the most
> experienced
> > > Apache and who keeps the true Open Source Spirit in the project.
> > >
> > > MAKE APACHE IGNITE GREAT AGAIN
> > >
> > > Sergi
> > >
> > >
> > >
> > > 2016-11-01 17:20 GMT+03:00 Anton Vinogradov :
> > >
> > >> Hi,
> > >>
> > >> Since everything works fine, I see no reason to change anything, so,
> > >> Dmitriy Setrakyan is a proven candidate.
> > >> But, anyways, I cannot but mention another good candidate, who works
> a lot
> > >> to build this community, it is Denis Magda.
> > >>
> > >> On Tue, Nov 1, 2016 at 4:34 PM, Konstantin Boudnik 
> wrote:
> > >>
> > >>> As per the [VOTE] we held back in 2015, I'd like to start a
> discussion
> > >>> about
> > >>> the PMC Chair for the next year. The original [VOTE] can be found in
> [1]
> > >>>
> > >>> Please make your nominations. Once we have the list of the candidates
> > >> we'll
> > >>> start the [VOTE] to determine the "lucky" winner.
> > >>>
> > >>> [1] https://lists.apache.org/thread.html/
> 55ee3b1c07f6e37ff06b0ab8caa4ac
> > >>> 13443b20ca2275546a60055964@1444775452@%3Cdev.ignite.apache.org%3E
> > >>>
> > >>> --
> > >>> Take care,
> > >>>  Cos
> > >>>
> > >>>
> > >>
> >
>

Re: [DISCUSS] PMC Chair rotation time

2016-11-02 Thread Konstantin Boudnik 
Just to reiterate the original premise for the rotation [1]:

- it provides an opportunity to anyone in the PMC to try this hat on and get
more involved in the inner-workings of the ASF and see how the board operates
- it guarantees that once you're a chair you aren't stuck holding the bag
forever and can pass it on if your time allocation changes
- such a policy makes the PMC very transparent


It ain't about supervision, as Chair doesn't have any magical powers over the
PMC. It is mostly about helping the board to provide a better view into the
project and be the representative of the board in the PMC. Most of the time it
is boring, but once in a while it might require quite a bit of an ability to
negotiate with people and be tasteful, if a situation gets sensitive for
whatever reason. Being a Chair doesn't mean he or she will lead the technical
side of the project: this responsibility comes as a consequence of one's merit,
rather than an official title of a sort.

[1] https://is.gd/bnVoaa

Cheers,
  Cos

On Tue, Nov 01, 2016 at 02:31PM, Denis Magda wrote:
> Fully support Cos’s proposal. 
> 
> It’s always a good intention to rotate positions like this even if
> everything runs smooth under a supervision of the present chair. Moreover,
> Dmitriy deserved some time to relax for the great job he did under this role 
> :)
> 
> From my side I would propose one more nominee - Valentin Kulichenko who
> brings significant efforts spreading out the knowledge in and out of the
> community, spends enormous amount of time assisting Ignite community and
> contributes to the overall future of the project.
> 
> As for my position, I’m not going to play mannerly games and would say that
> I’m ready to take over this role if the community decides so. Why? This is a
> matter of curiosity and abilities to make and learn more simply because
> you’ll be responsible for something new.
> 
> —
> Denis
> 
> > On Nov 1, 2016, at 8:00 AM, Sergi Vladykin  wrote:
> > 
> > I'd say that the most proved candidate is Vladimir Putin :) But I want to
> > nominate some more trusted guys to make sure that our election is true and
> > representative:
> > 
> > 1. I want to nominate Vladimir Ozerov, who plays a big role in our
> > engineering efforts to make Apache Ignite successful.
> > 
> > 2. Also I'd like to nominate Konstantin Boudnik who is the most experienced
> > Apache and who keeps the true Open Source Spirit in the project.
> > 
> > MAKE APACHE IGNITE GREAT AGAIN
> > 
> > Sergi
> > 
> > 
> > 
> > 2016-11-01 17:20 GMT+03:00 Anton Vinogradov :
> > 
> >> Hi,
> >> 
> >> Since everything works fine, I see no reason to change anything, so,
> >> Dmitriy Setrakyan is a proven candidate.
> >> But, anyways, I cannot but mention another good candidate, who works a lot
> >> to build this community, it is Denis Magda.
> >> 
> >> On Tue, Nov 1, 2016 at 4:34 PM, Konstantin Boudnik  wrote:
> >> 
> >>> As per the [VOTE] we held back in 2015, I'd like to start a discussion
> >>> about
> >>> the PMC Chair for the next year. The original [VOTE] can be found in [1]
> >>> 
> >>> Please make your nominations. Once we have the list of the candidates
> >> we'll
> >>> start the [VOTE] to determine the "lucky" winner.
> >>> 
> >>> [1] https://lists.apache.org/thread.html/55ee3b1c07f6e37ff06b0ab8caa4ac
> >>> 13443b20ca2275546a60055964@1444775452@%3Cdev.ignite.apache.org%3E
> >>> 
> >>> --
> >>> Take care,
> >>>  Cos
> >>> 
> >>> 
> >> 
>

Re: Updating Ignite Version on Apache Camel Side

2016-11-02 Thread Denis Magda 
Perfect, thanks!

—
Denis

> On Nov 2, 2016, at 10:46 AM, Raul Kripalani  wrote:
> 
> 
> Done.
> 
> 
>  
> 
> 
> camel-ignite: Update Ignite to v1.7.0. · apache/camel@210502e 
> 
> 
> 
>  
> camel - Mirror of Apache Camel                              
> 
> GITHUB.COM 
> 
> 
> Cheers.
> 
> ---
> Raúl Kripalani
> linkedin.com/in/raulkripalani  | 
> evosent.com 
> 
>  | blog: raul.io 
>  
> | skype: raul.fuse
> 
> On Wed 02 Nov 2016 at 17:34 r...@evosent.com  > wrote:
> Sure, working on it!
> 
> ---
> Raúl Kripalani
> linkedin.com/in/raulkripalani  | 
> evosent.com 
> 
>  | blog: raul.io 
>  
> | skype: raul.fuse
> 
> On Wed 02 Nov 2016 at 17:27 Denis Magda <> wrote:
> Hi Raul,
> 
> Would you mind updating the version of Ignite that is used on Apache Camel 
> side? The one that is used presently is quite old (1.5.0.final).
> 
> —
> Denis
> 
>> Begin forwarded message:
>> 
>> From: Denis Magda >
>> Subject: Page with external integrations 
>> Date: October 27, 2016 at 4:11:08 PM PDT
>> To: dev@ignite.apache.org , Raul Kripalani 
>> >
>> 
>> Igniters,
>> 
>> I’ve prepared the page that includes all the external projects/products that 
>> integrate with Apache Ignite. 
>> https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations 
>> 
>> 
>> Main purpose of this page is to track these integrations and update the 
>> owning party when a new version of Ignite gets rolled out so that sources 
>> and documentation can be renewed there if it’s needed.
>> 
>> Raul, would you mind updating the version of Ignite that is used on Apache 
>> Camel side? The one that is used presently is quite old (1.5.0.final).
>> 
>> —
>> Denis

Fwd: Updating Ignite Version on Apache Camel Side

2016-11-02 Thread Raul Kripalani 
Done.
https://github.com/apache/camel/commit/210502e22bfa0eb313fcd57ace8baa4761122395
https://github.com/apache/camel/commit/210502e22bfa0eb313fcd57ace8baa4761122395
https://polymail.io/?utm_source=polymail_medium=referral_campaign=link-preview

https://github.com/apache/camel/commit/210502e22bfa0eb313fcd57ace8baa4761122395

https://github.com/apache/camel/commit/210502e22bfa0eb313fcd57ace8baa4761122395

Cheers.

---

Raúl Kripalani

http://linkedin.com/in/raulkripalani
 | 
http://evosent.com/?utm_source=email_medium=email_campaign=evosent_raul
 | blog: 
http://raul.io/?utm_source=email_medium=email_campaign=evosent_raul
 | skype: raul.fuse

On Wed 02 Nov 2016 at 17:34 r...@evosent.com <
mailto:r...@evosent.com
> wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }

Sure, working on it!

---

Raúl Kripalani

http://linkedin.com/in/raulkripalani
 | 
http://evosent.com/?utm_source=email_medium=email_campaign=evosent_raul
 | blog: 
http://raul.io/?utm_source=email_medium=email_campaign=evosent_raul
 | skype: raul.fuse

On Wed 02 Nov 2016 at 17:27 Denis Magda

<
mailto:Denis Magda 
> wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }

Hi Raul,

Would you mind updating the version of Ignite that is used on Apache Camel 
side? The one that is used presently is quite old (1.5.0.final).

—

Denis

Begin forwarded message:

From:

Denis Magda <
mailto:dma...@gridgain.com
>

Subject:

Page with external integrations

Date:

October 27, 2016 at 4:11:08 PM PDT

To:

mailto:dev@ignite.apache.org
, Raul Kripalani <
mailto:ra...@apache.org
>

Igniters,

I’ve prepared the page that includes all the external projects/products that 
integrate with Apache Ignite. 

https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations

Main purpose of this page is to track these integrations and update the owning 
party when a new version of Ignite gets rolled out so that sources and 
documentation can be renewed there if it’s needed.

Raul,

would you mind updating the version of Ignite that is used on Apache Camel 
side? The one that is used presently is quite old (1.5.0.final).

—

Denis

Re: Apache Ignite 1.8 Release

2016-11-02 Thread Denis Magda 
Roman,

Sure, it makes sense to include this into the release highlighting that 
presently Ignite provides a limited support.

Please create a pull-request and send a message (not a part of this discussion) 
to the dev list asking for review.

—
Denis

> On Nov 1, 2016, at 6:46 PM, Roman Shtykh  wrote:
> 
> Igniters,
> I have implemented a basic set of Redis protocol commands a while ago -- 
> those I could wrap Ignite's REST/memcached commands with.
> Since Redis protocol has a richer set of commands compared to REST's, there 
> are some limitations in the current implementation (and I think it will be 
> not that easy to implement more advanced commands). Please see the ticket, it 
> has a list of commands and the limitation described.
> https://issues.apache.org/jira/browse/IGNITE-3066
> Can it be reviewed, and possibly receive recommendations how to remove the 
> limitations? Probably it can be considered for 1.8 release.
> -Roman
> 
> 
>On Wednesday, October 26, 2016 1:26 AM, Denis Magda  
> wrote:
> 
> 
> Igniters,
> 
> Looking at the discussions that happen on our dev list regarding Ignite's 
> improvements I should say that we’re ready to prepare and roll out one more 
> Ignite minor release before the end of the year - Apache Ignite 1.8.0. My 
> proposal is to make it available by mid November, somewhere around November 
> 21st.
> 
> Personally, the following features have to be included in it due to the 
> importance and readiness:
> DML Support: https://issues.apache.org/jira/browse/IGNITE-2294 
> 
> PHP PDO Support from ODBC side: 
> https://issues.apache.org/jira/browse/IGNITE-3865 
> 
> Ignite as a second level cache for .NET Entity Framework: 
> https://issues.apache.org/jira/browse/IGNITE-1915 
> 
> 
> The first feature make it realistic to execute INSERT, UPDATE, DELETE queries 
> over Ignite caches using Java APIs or by connecting to a cluster using JDBC 
> or ODBC drivers and send DML queries not only from Java side but from a 
> variety of technologies and tools. As an example, the second feature from the 
> list is intended to enable support for PHP by mixing DML with SELECT SQL 
> queries plus sending them over Ignite’s ODBC driver. 
> 
> The third feature will allow to broaden the usage of Apache Ignite .NET 
> client among .NET community by providing more advanced support for .NET 
> Entity Framework.
> 
> Feature owners of the above mentioned tickets, please provide the current 
> status on them?
> 
> If anyone else wants to see something else as a part of Ignite 1.8 and ready 
> to contribute it by the mid of November please reply to the thread as well.
> 
> Regards,
> Denis
>

Fwd: Updating Ignite Version on Apache Camel Side

2016-11-02 Thread Raul Kripalani 
Sure, working on it!

---

Raúl Kripalani

http://linkedin.com/in/raulkripalani
 | 
http://evosent.com/?utm_source=email_medium=email_campaign=evosent_raul
 | blog: 
http://raul.io/?utm_source=email_medium=email_campaign=evosent_raul
 | skype: raul.fuse

On Wed 02 Nov 2016 at 17:27 Denis Magda

<
mailto:Denis Magda 
> wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }

Hi Raul,

Would you mind updating the version of Ignite that is used on Apache Camel 
side? The one that is used presently is quite old (1.5.0.final).

—

Denis

Begin forwarded message:

From:

Denis Magda <
mailto:dma...@gridgain.com
>

Subject:

Page with external integrations

Date:

October 27, 2016 at 4:11:08 PM PDT

To:

mailto:dev@ignite.apache.org
, Raul Kripalani <
mailto:ra...@apache.org
>

Igniters,

I’ve prepared the page that includes all the external projects/products that 
integrate with Apache Ignite. 

https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations

Main purpose of this page is to track these integrations and update the owning 
party when a new version of Ignite gets rolled out so that sources and 
documentation can be renewed there if it’s needed.

Raul,

would you mind updating the version of Ignite that is used on Apache Camel 
side? The one that is used presently is quite old (1.5.0.final).

—

Denis

Re: Updating Ignite Interpreter Guide on Zeppelin

2016-11-02 Thread Denis Magda 
Andrey, thanks a lot!

—
Denis

> On Nov 2, 2016, at 10:24 AM, Andrey Gura  wrote:
> 
> Hi, all.
> 
> I've update Ignite interpreter docs in Apache Zeppelin repository. PR:
> https://github.com/apache/zeppelin/pull/1581
> 
> If you have some comments please notify.
> 
> On Tue, Nov 1, 2016 at 4:08 PM, Andrey Gura  wrote:
> 
>> Hi, Denis.
>> 
>> I'll try to fix this situation and notify you and community in this thread.
>> 
>> On Thu, Oct 27, 2016 at 11:25 PM, Denis Magda  wrote:
>> 
>>> Andrey G.,
>>> 
>>> As a maintainer of Ignite and Zeppelin Integration please contact
>>> Zeppelin guys asking them to update the following page
>>> https://zeppelin.apache.org/docs/0.6.2/interpreter/ignite.html <
>>> https://zeppelin.apache.org/docs/0.6.2/interpreter/ignite.html>
>>> 
>>> The page still refers to Ignite of version 1.2.0-incubating and they
>>> still promise to include Ignite in the binary release. Please coordinate
>>> with them making sure that the doc refers to Ignite 1.7.0 and that they
>>> finally will make Ignite a part of their release.
>>> 
>>> Agreed?
>>> 
>>> —
>>> Denis
>> 
>> 
>>

Re: Updating Ignite Interpreter Guide on Zeppelin

2016-11-02 Thread Andrey Gura 
Hi, all.

I've update Ignite interpreter docs in Apache Zeppelin repository. PR:
https://github.com/apache/zeppelin/pull/1581

If you have some comments please notify.

On Tue, Nov 1, 2016 at 4:08 PM, Andrey Gura  wrote:

> Hi, Denis.
>
> I'll try to fix this situation and notify you and community in this thread.
>
> On Thu, Oct 27, 2016 at 11:25 PM, Denis Magda  wrote:
>
>> Andrey G.,
>>
>> As a maintainer of Ignite and Zeppelin Integration please contact
>> Zeppelin guys asking them to update the following page
>> https://zeppelin.apache.org/docs/0.6.2/interpreter/ignite.html <
>> https://zeppelin.apache.org/docs/0.6.2/interpreter/ignite.html>
>>
>> The page still refers to Ignite of version 1.2.0-incubating and they
>> still promise to include Ignite in the binary release. Please coordinate
>> with them making sure that the doc refers to Ignite 1.7.0 and that they
>> finally will make Ignite a part of their release.
>>
>> Agreed?
>>
>> —
>> Denis
>
>
>

[GitHub] ignite pull request #1204: Ignite 1.5.33

2016-11-02 Thread dkarachentsev 
GitHub user dkarachentsev opened a pull request:

https://github.com/apache/ignite/pull/1204

Ignite 1.5.33



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

$ git pull https://github.com/gridgain/apache-ignite ignite-1.5.33

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

https://github.com/apache/ignite/pull/1204.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 #1204


commit 76191ff39456a30246df3aca7c026773d00a8446
Author: vozerov-gridgain 
Date:   2016-03-21T07:36:26Z

IGNITE-2861: Added missing Apache headers.

commit ee5ea53bf9c4ad897459466e0b9b5447fc93ec2a
Author: vozerov-gridgain 
Date:   2016-03-22T06:20:32Z

IGNITE-2869: IGFS: Slightly improved serialization of IgfsListingEntry.

commit 218132dc0c3764966294a5f29ad480af4af7b0ff
Author: vozerov-gridgain 
Date:   2016-03-22T06:23:29Z

IGNITE-2868: IGFS: Increased trash concurrency from 16 to 64.

commit e886ad0aa800cddb3308fa5f8400902e5879ee3c
Author: vozerov-gridgain 
Date:   2016-03-22T07:28:13Z

IGNITE-2811: IGFS: Optimized properties handling.

commit 8d95ebacaa01f3f9271a1ce0d1b991dfead1d0c1
Author: vozerov-gridgain 
Date:   2016-03-22T09:06:51Z

IGNITE-2871: IGFS: Removed "path" from IgfsEntryInfo. Purge event is never 
fired now, it will be fixed as a part of IGNITE-1679.

commit b286facc4b8c44ab1628039dded6c7527760df73
Author: vozerov-gridgain 
Date:   2016-03-22T09:34:35Z

IGNITE-2806: IGFS: Implemented relaxed consistency model.

commit 26f115734e7262d4b4b60f1c6016783f67c66986
Author: vozerov-gridgain 
Date:   2016-03-22T09:46:23Z

IGFS: Added misssing "final" modifiers to FileSystemConfiguration defaults.

commit 00a0e4b51c299871ff690bbe6d462cf80dae045e
Author: vozerov-gridgain 
Date:   2016-03-24T07:35:43Z

IGNITE-2878: IGFS: Optimzied serialization of IgfsListingEntry and 
properties map.

commit 01a6e86ec4e19d372b8efbc5c497c84f4238a46c
Author: vozerov-gridgain 
Date:   2016-03-24T10:28:30Z

IGNITE-2876: Fixed possible starvation in system pool caused by 
IgfsBlockMessage. This closes #575.

commit 59705e008267b1d5926410f95c68bb8ffb8cd93c
Author: vozerov-gridgain 
Date:   2016-03-24T11:29:35Z

IGNITE-2883: IGFS: Now IPC messages are handled in a dedicated thread pool.

commit 0412c9bfd89b8d2a377588e908f1012c845ac5bc
Author: Alexey Kuznetsov 
Date:   2016-03-30T04:43:19Z

Added detail info about keys count in partitions for offheap and swap.

commit 28d2a7bf7f35ec4b51fba872ace47cdbc255ded8
Author: Alexey Kuznetsov 
Date:   2016-03-30T07:42:12Z

Minor change to Visor classes: added setters for name and queryMetrics 
properties.

commit a70d2dc48c42f23b1ea64c2a219560efa44fb99f
Author: Alexey Kuznetsov 
Date:   2016-04-04T07:14:42Z

Minor fix for Visor query metrics.

commit ec2ec9965ae03ef3666b2035a13f444cf2765aec
Author: dkarachentsev 
Date:   2016-03-30T10:29:36Z

Now cache plugins are able to unwrap entries passed to EntryProcessor.

commit e85a7170534cb66f40386cba689cfe632f4e66db
Author: ashutak 
Date:   2016-04-05T11:56:01Z

ignite-2835: Fixed BinaryObjectOffHeapImpl leakage to public code

commit d33b4340a68553e59e4adecf78fea79af55bf2ae
Author: sboikov 
Date:   2016-04-05T13:42:50Z

ignite-2835 Minor test changes.

commit 2397552daf6d8cff9b59515c1c8983abdc60f5f4
Author: vdpyatkov 
Date:   2016-04-05T15:03:55Z

IGNITE-2822
Continuous query local listener can be notified with empty list of events

commit 87f7522c56b5735442f8d52dbc63756de53f2464
Author: sboikov 
Date:   2016-04-06T06:46:47Z

gridgain-7.5.11 Increased default affinity history size.

commit 86347272e712a0e61a5a763dda3458fde79f29c4
Author: Anton Vinogradov 
Date:   2016-04-06T08:35:36Z

IGNITE-2947
BinaryContext doesn't honor custom loader set through 
IgniteConfiguration.classLoader

commit b2c934d7abe6dfe86e1d09ec592875df987f2120
Author: Alexey Kuznetsov 
Date:   2016-04-06T10:31:21Z

 IGNITE-2963 Fixed special case with Date for Oracle JDBC driver.

commit e7ab8eef504cdcf8987941e8b7a552ada451aec8
Author: sboikov 
Date:   2016-04-06T14:38:04Z

gridgain-7.5.11 Affinity history cleanup ignoring client discovery event.

commit d92e617a71c31ccaa3fd6e4954aa4ccaf494733c
Author: Valentin Kulichenko 
Date:   2016-04-07T01:10:45Z

IGNITE-2951 - Stability fixes for cluster with many clients

commit

[GitHub] ignite pull request #563: ignite-2797 Fixed hanging of transactions with tim...

2016-11-02 Thread agura 
Github user agura closed the pull request at:

https://github.com/apache/ignite/pull/563


---
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 #873: Ignite 2968

2016-11-02 Thread agura 
Github user agura closed the pull request at:

https://github.com/apache/ignite/pull/873


---
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 #888: Ignite 2968 part

2016-11-02 Thread agura 
Github user agura closed the pull request at:

https://github.com/apache/ignite/pull/888


---
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 #933: Ignite-2968-1

2016-11-02 Thread agura 
Github user agura closed the pull request at:

https://github.com/apache/ignite/pull/933


---
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 #943: Ignite-2968-2

2016-11-02 Thread agura 
Github user agura closed the pull request at:

https://github.com/apache/ignite/pull/943


---
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 #964: Ignite-2968-3

2016-11-02 Thread agura 
Github user agura closed the pull request at:

https://github.com/apache/ignite/pull/964


---
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 #1203: Ignite 3074

2016-11-02 Thread kdudkov 
GitHub user kdudkov opened a pull request:

https://github.com/apache/ignite/pull/1203

Ignite 3074



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

$ git pull https://github.com/gridgain/apache-ignite ignite-3074

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

https://github.com/apache/ignite/pull/1203.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 #1203


commit 40d4b6ac6a71ed541d20018cf7deb2fb9b9bbb9b
Author: vozerov-gridgain 
Date:   2016-09-05T08:35:26Z

IGNITE-3834: Fixed a problem with BinaryMarshaller handles resolution.

commit b640b8ed7f9ce0fdf24392404eedbc1f54c9063c
Author: shtykh_roman 
Date:   2016-09-05T08:43:06Z

IGNITE-3687: Updated StormStreamer dependencies. - Fixes #959.

Signed-off-by: shtykh_roman 

commit 42963e6c99e9b282972e6ad67a813a8038cf580f
Author: Alexander Paschenko 
Date:   2016-09-05T11:10:39Z

IGNITE-3817: Fixed binary object re-build with missing schema.

commit df8163f1ad3a390bb8d51b0eb2f378b5b3663025
Author: Andrey V. Mashenkov 
Date:   2016-09-05T11:15:59Z

IGNITE-3743: ODBC: Added procedure call escape sequence support. This 
closes #1008.

commit e3533010b584ba986196f9c7dbc36359aebd829e
Author: Igor Sapego 
Date:   2016-09-05T12:02:07Z

IGNITE-3819: ODBC: Improved error logging. This closes #1024.

commit 008cf64429f40635e396a71f2c0aaf184077ff2b
Author: Andrey V. Mashenkov 
Date:   2016-09-05T12:17:53Z

IGNITE-3741: ODBC: Added character escape support to expression parser. 
This closes #1004.

commit bf9371a3ddb020209a6b031e11282706e19c58cb
Author: vozerov-gridgain 
Date:   2016-09-05T14:05:05Z

IGNITE-3611: IGFS: Slight refactoring to listPaths() and listFiles() 
methods.

commit 2c397d2fb8851b25aa5f0a5589ad1deffbe7eee9
Author: Andrey V. Mashenkov 
Date:   2016-09-05T14:38:47Z

IGNITE-2629: ODBC: Requests are now processed asynchronously in separate 
thread pool. This closes #996.

commit 355082958b476009179254df9be20e225179cb7c
Author: Andrey V. Mashenkov 
Date:   2016-09-05T15:06:27Z

IGNITE-2833: GridCacheTtlManager pending queue retention size optimization.

commit 8970b3e3a36b18274b451fddf365627ba23459d6
Author: Igor Sapego 
Date:   2016-09-05T15:15:11Z

IGNITE-3628: ODBC: Added ability to configure page size in DSN, changed 
default value from 32 to 1024. This closes #1014.

commit 69632c8fa7a62b5d24c46f7440c83bcdb6151fd2
Author: Alexey Kuznetsov 
Date:   2016-09-06T08:26:54Z

Fixed RAT license header check.

commit e23a94fbab4040f60b7a8ef3638aaebe4b9ba5f6
Author: sboikov 
Date:   2016-09-06T08:34:14Z

Fixed GridQueryParsingTest.

commit 385355a157993f4d78ced551bbaa168181748a7d
Author: sboikov 
Date:   2016-09-06T09:09:38Z

GridNearOptimisticTxPrepareFuture: fixed javadoc warning.

commit bdc1b10cabcefb6684adcdb22bb6106e44148516
Author: sboikov 
Date:   2016-09-06T11:45:01Z

IGNITE-2208 Queries with object arguments doesn't work wth 
BinaryMarshaller: use 'toBinary' for arguments conversion.

commit 31b9bb84dd29259121759c655bac6247d2b93285
Author: shtykh_roman 
Date:   2016-09-07T05:35:31Z

IGNITE-3809: Fix for ArrayIndexOutOfBoundsException in GridUnsafeLru. - 
Fixes #1017.

Signed-off-by: shtykh_roman 

commit 224cae1dd5dc5d95843c6ea1a72f61f27ea35cb4
Author: sboikov 
Date:   2016-09-07T07:18:20Z

Fixed IgniteCacheExpiryPolicyAbstractTest.testZeroOnAccess.

commit b5121adff860d96e5954d3466137854f8fae4c27
Author: sboikov 
Date:   2016-09-07T09:44:24Z

IGNITE-2629: ODBC: GridNioAsyncNotifyFilter should process onSessionOpened 
synchronously

commit d672f2989582fe7259260a25f0a8ed26f31f5b09
Author: Igor Sapego 
Date:   2016-09-07T11:28:06Z

IGNITE-3705: CPP: Fixed warnings for MSVC 14.0. This closes #1038.

commit 121b89b07990068a31d384da8d6f3c781cf0efb8
Author: sboikov 
Date:   2016-09-07T11:36:51Z

Fixed NPE in GridCacheAbstractFullApiSelfTest in multi jvm tests.

commit 2703648f380037a833e55a52a6c33e844a9e48fc
Author: tledkov-gridgain 
Date:   2016-09-07T14:12:34Z

IGNITE-3423 IGFS: Fixed incorrect result of IgfsGlobalSpaceTask for IGFS of 
unlimited size. This closes #1032.

commit 88d027d280ba437a69d8100db1e0e6a5f034188c
Author: tledkov-gridgain 
Date:   2016-09-07T14:20:25Z

IGNITE-3851 IGFS: Support direct PROXY mode invocation in method: exists. 
This closes #1039.

commit

Re: Talking to Ignite From PHP

2016-11-02 Thread Igor Sapego 
Denis,

I believe that you should switch to DML branch (ignite-2294),
and then merge ignite-3910 into it.

That should be enough. Please let me know if there are any issues.

Best Regards,
Igor

On Wed, Nov 2, 2016 at 3:12 AM, Denis Magda  wrote:

> Igor,
>
> I’m planning to prepare a blog post about our PHP + PDO + Ignite
> integration and referring to the documentation template available for now
> https://apacheignite.readme.io/docs/pdo-interoperability
>
> Considering that the fixes and improvements you did for Ignite ODBC driver
> in order to support PDO have not been released yet what is a valid branch
> number if I want to do the following:
> - connect to the cluster from PHP code.
> - populate a cache using DML INSERT command.
> - query the data with the usage of SQL.
>
> —
> Denis
>
>

Re: IgniteSemaphore and failoverSafe flag

2016-11-02 Thread Andrey Gura 
Vladisav,

I've ran this test with partitioned cache and 1 backup and with replicated
cache (4 nodes in topology). Behavior is the same. I think it is bug. But
the first I wanted make sure that I understand failoverSafe flag correctly.

Thank you for reply. I'll create ticket.

On Tue, Nov 1, 2016 at 8:48 PM, Vladisav Jelisavcic 
wrote:

> Hi,
>
> when failoverSafe == true, semaphore should silently redistribute the
> permits acquired on the failing node.
> If failoverSafe is set to false, exception is thrown to every node
> attempting to acquire.
>
> It seems to me that when the first instance left topology,
> no backups were available (this is similar to:
> https://issues.apache.org/jira/browse/IGNITE-3386).
> This should be fixed (semaphore should be recreated when create==true, as
> suggested by Denis in the ticket).
>
> It should be a minor fix, will be ready for 1.8.
>
> Best regards,
> Vladisav
>
>
>
>
>
>
>
>
> On Tue, Nov 1, 2016 at 5:41 PM, Andrey Gura  wrote:
>
> > Hi all!
> >
> > Guys, could somebody explain semantic of failoverSafe flag in
> > IgniteSemaphore. From my point of view the test below should work but it
> > fails:
> >
> > public void testFailoverReleasePermits() throws Exception {
> > Ignite ignite = grid(0);
> >
> > IgniteSemaphore sem = ignite.semaphore("sem", 1, true, true);
> >
> > sem.acquire(1);
> >
> > ignite.close();
> >
> > U.sleep(5000);
> >
> > ignite = grid(1);
> >
> > sem = ignite.semaphore("sem", 1, true, true);
> >
> > boolean acquire = sem.tryAcquire(1, 5000, TimeUnit.MILLISECONDS);
> >
> > assertTrue(acquire); // fails here
> > }
> >
> > From my point of view permit should be available after the first ignite
> > instance left topology.
> >
>

[jira] [Created] (IGNITE-4165) ignite-spark module scaladocs isn't included in Scala API docs

2016-11-02 Thread Andrey Gura (JIRA) 
Andrey Gura created IGNITE-4165:
---

 Summary: ignite-spark module scaladocs isn't included in Scala API 
docs
 Key: IGNITE-4165
 URL: https://issues.apache.org/jira/browse/IGNITE-4165
 Project: Ignite
  Issue Type: Bug
Reporter: Andrey Gura


Ignie Scala API docs contains only Scalar scaladoc but not ignite-spark 
scaladoc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4164) Add support for parallel loading of caches using custom SQL load queries in org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#loadCache

2016-11-02 Thread Anghel Botos (JIRA) 
Anghel Botos created IGNITE-4164:


 Summary: Add support for parallel loading of caches using custom 
SQL load queries in 
org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#loadCache
 Key: IGNITE-4164
 URL: https://issues.apache.org/jira/browse/IGNITE-4164
 Project: Ignite
  Issue Type: Improvement
  Components: SQL
Affects Versions: 1.7
Reporter: Anghel Botos


Please add support for parallel loading of caches using custom SQL load queries 
in org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore#loadCache. For the 
moment this is not possible, as the current implementation performs the load 
for each entity type in the cache using a single 
{{LoadCacheCustomQueryWorker}}, as opposed to the the approach that is used 
when no custom SQL queries are provided for the load, where for each entity 
type, the load is distributed across several threads based on some ranges.

While it may not be possible to support parralel load with any custom SQL query 
(as this would mean that Ignite would have to somehow understand the meaning of 
that custom query), it would still be a significant improvement if it would be 
possible to have the parallel load when providing a custom {{WHERE}} clause for 
each entity type (instead of a full custom query).




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4163) Wrong SQL generated by org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery

2016-11-02 Thread Anghel Botos (JIRA) 
Anghel Botos created IGNITE-4163:


 Summary: Wrong SQL generated by 
org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
 Key: IGNITE-4163
 URL: https://issues.apache.org/jira/browse/IGNITE-4163
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 1.7
Reporter: Anghel Botos


The SQL statement generated by 
org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
 looks like this:

{{SELECT KEY_COLUMN_1,KEY_COLUMN_2 FROM (SELECT KEY_COLUMN_1,KEY_COLUMN_2, 
ROWNUM() AS rn FROM SOME_TABLE ORDER BY KEY_COLUMN_1,KEY_COLUMN_2) WHERE 
mod(rn, ?) = 0}}

For Oracle this is incorrect, as Oracle does not have a {{ROWNUM()}} function. 
For the above query the following error is thrown: {{ORA-00923: FROM keyword 
not found where expected}}

Regarding row numbering Oracle has:
* a {{ROWNUM}} pseudocolumn, in which case the query should have {{ROWNUM AS 
rn}}
* a {{ROW_NUMBER()}} function, in which case the query would become more 
complicated. See 
https://docs.oracle.com/database/121/SQLRF/functions170.htm#SQLRF06100 for more 
details about {{ROW_NUMBER()}}

Please make the neccessary adjustments to either {{BasicJdbcDialect}} or 
{{OracleDialect}} so that a correct query is produced.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Cache consistency

2016-11-02 Thread Vladislav Pyatkov 
Hi Alisher,

At first I assume the discussion need to be moved to user-forum (
u...@ignite.apache.org).

If you have 2 backups (in case you have enough nodes) this mean you can
loose 2 node, without afraid to loose data. In case you have a fail more
than the 2 nodes, it is mean you have incomplete(only part of data has
available) data.

In general, If you are loosing more nodes than backups you are have, this
must be signal: "These inconsistent!".

Also you can divided your nodes by specification: group of backups and
group of primary, using RendezvousAffinityFunction#setAffinityBackupFilter.

On Wed, Nov 2, 2016 at 11:11 AM, Alisher Alimov 
wrote:

> Hi!
>
> I have a question about data consistency in cluster, if there are any
> mechanism for checking that cache is in consistency state (no lost
> data/partitions)
>
> For example I have a cluster with N nodes, long compute job that calculate
> monthly revenue on huge amount of data. Data is transaction log that stored
> in cache “transactions"  (where key is transaction id, value
> transaction amount). Cache backups = 2.
>
> First case.
>
> 1. We load huge amount of data in cache "transactions"
> 2. All is fine
> 3. Run simple compute job that sum values in transaction log  ( Float::sum
> )
> 4. Compute job run on all nodes except n1,n2
> 5. We lost n1 node, than n2 node that stored backup of n1 node
> 6. Ignite found that node n1 and n2 are down and rebalancing data
> 7. Compute job was completed
>
> Second case.
>
> 1. We load huge amount of data in cache "transactions"
> 2. All is fine
> 3. We lost n1 node, then n2 node that stored backup of n1 node
> 4. Ignite found that node n1 and n2 are down and rebalancing data
> 5. Run simple compute job that sum values in transaction log  ( (a,b) ->
> a+b )
>
> So questions:
> - what result we can retrieve in first case from compute job?
> - at second case we run compute job on cache that is not in consistency
> state  (partitions that belongs to n1, n2 nodes was lost) but Ignite cache
> will work fine and allow us to run ComputeJob on cache and doesn’t tell us
> that some data was lost, isn’t it?
>
>
> With best regards
> Alisher Alimov
> alimovalis...@gmail.com
>
>
>
>
>

Cache consistency

2016-11-02 Thread Alisher Alimov 
Hi!

I have a question about data consistency in cluster, if there are any mechanism 
for checking that cache is in consistency state (no lost data/partitions)

For example I have a cluster with N nodes, long compute job that calculate 
monthly revenue on huge amount of data. Data is transaction log that stored in 
cache “transactions"  (where key is transaction id, value 
transaction amount). Cache backups = 2.

First case.

1. We load huge amount of data in cache "transactions"
2. All is fine
3. Run simple compute job that sum values in transaction log  ( Float::sum )
4. Compute job run on all nodes except n1,n2
5. We lost n1 node, than n2 node that stored backup of n1 node
6. Ignite found that node n1 and n2 are down and rebalancing data
7. Compute job was completed

Second case.

1. We load huge amount of data in cache "transactions"
2. All is fine
3. We lost n1 node, then n2 node that stored backup of n1 node
4. Ignite found that node n1 and n2 are down and rebalancing data
5. Run simple compute job that sum values in transaction log  ( (a,b) -> a+b )

So questions:
- what result we can retrieve in first case from compute job?
- at second case we run compute job on cache that is not in consistency state  
(partitions that belongs to n1, n2 nodes was lost) but Ignite cache will work 
fine and allow us to run ComputeJob on cache and doesn’t tell us that some data 
was lost, isn’t it?


With best regards
Alisher Alimov
alimovalis...@gmail.com