Re: Storing deserialized value when indexing is enabled

[Pavel Tupitsyn]

Looks like a known issue to me, I've linked related tickets in Jira:

https://issues.apache.org/jira/browse/IGNITE-2417
https://issues.apache.org/jira/browse/IGNITE-3347

On Thu, Nov 24, 2016 at 12:13 AM, Denis Magda  wrote:

> Val,
>
> Yeah, the code is like jungles in some places. Proposed a possible fix
> inside of the ticket.
>
> —
> Denis
>
> > On Nov 23, 2016, at 1:01 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
> >
> > Denis,
> >
> > CacheObjectBinaryProcessorImpl calls super and preserves the value of
> > storeVal flag. It seems to me that it's then used in
> > BinaryObjectImpl.deserializeValue() causing the deserialized value to be
> > saved in memory. This doubles memory consumption in this scenario.
> >
> > I created a ticket: https://issues.apache.org/jira/browse/IGNITE-4293
> >
> > -Val
> >
> > On Wed, Nov 23, 2016 at 12:32 PM, Denis Magda  wrote:
> >
> >> Val,
> >>
> >> You get confused by IgniteCacheObjectProcessorImpl.contextForCache(…)
> >> method.
> >>
> >> When binary marshaller is enable the default processor is
> >> CacheObjectBinaryProcessorImpl and when contextForCache(…) gets called
> on
> >> its side the processor will create CacheObjectBinaryContext which, in
> its
> >> turn, has binaryEnabled field that in fact controls an object
> >> deserialization on a server side.
> >>
> >> —
> >> Denis
> >>
> >>> On Nov 23, 2016, at 12:14 PM, Valentin Kulichenko <
> >> valentin.kuliche...@gmail.com> wrote:
> >>>
> >>> Folks,
> >>>
> >>> It looks like we cache the deserialized value in case indexing is
> enabled
> >>> and a read operation happens on server side (e.g. affinity closure does
> >>> get() on primary node).
> >>>
> >>> This must be caused by this piece of code in
> >> IgniteCacheObjectProcessorImpl:
> >>>
> >>> boolean storeVal = ctx.config().isPeerClassLoadingEnabled() ||
> >>>   GridQueryProcessor.isEnabled(ccfg) ||
> >>>   !ccfg.isCopyOnRead();
> >>>
> >>> This actually means that we store deserialized values in case indexing
> is
> >>> configured even if copyOnRead is true. My understanding is that this
> is a
> >>> bug and GridQueryProcessor.isEnabled(ccfg) condition should be removed
> >> from
> >>> there (at least for the case when binary marshaller is used).
> >>>
> >>> Am I missing something?
> >>>
> >>> -Val
> >>
> >>
>
>

Re: Blogging about new .NET features

[Pavel Tupitsyn]

Denis, sure, I think I'll start with "What's new in Ignite.NET 1.8" and
write in more detail about big features later.

On Wed, Nov 23, 2016 at 9:34 PM, Denis Magda  wrote:

> Pavel,
>
> Do you mind blogging about ASP.NET session state [1] and Entity Framework
> 2nd level cache [2] support after 1.8 release goes public?
>
> Also I would remind everyone in the community that it’s always welcomed to
> share your experience or Ignite related news over blog posts. We track all
> the posts on this page.
> https://ignite.apache.org/blogs.html
>
>
> [1] https://apacheignite-net.readme.io/docs/aspnet-session-state-caching
> [2] https://apacheignite-net.readme.io/docs/entity-
> framework-second-level-cache
>
> —
> Denis
>

[GitHub] ignite pull request #1274: IGNITE-4205 CassandraCacheStore should start Igni...

[irudyak]

GitHub user irudyak opened a pull request:

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

IGNITE-4205 CassandraCacheStore should start IgniteThread threads in 
loadCache() method



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

$ git pull https://github.com/irudyak/ignite ignite-4205

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

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


commit 9940e5e6304ffbae317209ce496f235994cf34be
Author: Igor 
Date:   2016-11-24T05:41:09Z

utilysing  IgniteThreadFactory for ThreadPool created inside loadCache




---
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 #1273: IGNITE-4282: Javadoc broken.

[shroman]

GitHub user shroman opened a pull request:

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

IGNITE-4282: Javadoc broken.



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

$ git pull https://github.com/shroman/ignite ignite-4282

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

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


commit a89229ee53e5ccbbcadd0b6a7b245df1e9fb86a3
Author: shtykh_roman 
Date:   2016-11-24T01:44:38Z

IGNITE-4282: Javadoc broken.




---
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: [DISCUSS] PMC Chair rotation time

[Dmitriy Setrakyan]

Cos, I will start the vote soon. A bit over occupied with travel and
holidays at this moment.

On Mon, Nov 21, 2016 at 12:33 PM, Konstantin Boudnik  wrote:

> Ok,
>
> This was a great discussion, thanks for the deep insight, Roman!
>
> looks like this thread has stewed for a while and it is time to [VOTE]. The
> following candidates were put forward during the [DISCUSS] (in the order of
> their appearance on the thread):
>
>   Dmitriy Setrakyan
>   Vladimir Ozerov
>   Konstantin Boudnik
>   Valentin Kulichenko
>   Denis Magda
>   Branko Čibej
>
> Considering the number of the candidates I propose to use
> First-past-the-post
> voting, with a single-round/single winner rules, where the candidate
> collecting the most votes (not the majority) wins. [1]
>
> Dmitriy, would you do the honors and start the formal [VOTE]?
>
>
> [1] https://en.wikipedia.org/wiki/First-past-the-post_voting
>
> Thanks,
>   Cos
>
> On Thu, Nov 10, 2016 at 08:19PM, Roman Shaposhnik wrote:
> > On Wed, Nov 2, 2016 at 11:32 AM, Dmitriy Setrakyan
> >  wrote:
> > > 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.
> >
> > Sorry to come to this thread rather late, but I wanted to offer a
> somewhat
> > different perspective that hopefully can help reframe this discussion
> > a little bit.
> > Note, that what I'm about to say is coming from a non-coding (on Ignite)
> member
> > of the PMC. In fact, I stayed on the PMC after graduation more with my
> ASF
> > member hat on, rather than as somebody who wanted to directly contribute
> > to where the technology was going. My concern during your incubation days
> > was (and still is!) how well are you guys doing on the community
> development
> > front.
> >
> > If you recall, the diversity requirement (the fact that more than 80% of
> project
> > members work for the same company) came up during our graduation. While
> > it wasn't a blocking requirement it still was a very valid concern.
> Monocultures
> > are really nasty for open source communities.
> >
> > I think it would be fair to say that Ignite community hasn't really
> > improved much
> > diversity-wise since its graduation. And I honestly feel that this is,
> > to a larger
> > extent, because the focus is now missing. It was well understood that in
> order
> > to graduate the community had to do all it can to demonstrate a
> > positive trajectory
> > in that direction. And we did. But we kind of dropped the ball on it
> since.
> >
> > With that in mind, I offer my view on what a change in the Chair could
> > offer: a renewed
> > focus on community growth and development. If you agree with this
> premise than
> > somebody like Branko or Cos who could act as a forcing function to
> constantly
> > remind us about what else can we do to grow and develop this community
> would
> > be an ideal choice for the Chair (after all Branko's "tough love" was
> > probably the
> > most useful part of Ignite's experience in the Incubator).
> >
> > Now, of course, strictly speaking you don't have to be a Chair to do
> > that. But lets
> > face it -- that helps. And besides, a project's Chair doesn't really
> > have any special
> > powers when it comes to technological consensus, but anything that has
> to do
> > with external community the VP title that the chair gets can help quite
> a bit.
> >
> > Long story short: if Branko or Cos (as former mentors) would like to
> > commit to 6 more
> > months of the same hands-on mentorship focused on community development
> -- they
> > would have my wholehearted support.
> >
> > Thanks,
> > Roman (with my PMC member hat on).
>

Re: In-Memory SQL Grid

[Dmitriy Setrakyan]

I like SQL Grid, seems consistent. I think that DML support is huge for the
project!

D.

On Wed, Nov 23, 2016 at 12:08 PM, Denis Magda  wrote:

> Community,
>
> Frankly speaking, Ignite’s SQL support goes far beyond the notion of Data
> Grid starting from Apache Ignite 1.8.
> SQL in Ignite is no longer about distributed ANSI-99 SELECT queries only.
>
> It will be about the ability to connect to an Ignite Cluster not only from
> Java, .NET and C++ sides, that have their own SQL APIs, but, in general,
> from your favorite programming language or analytical tool by the usage of
> Ignite’s JDBC and ODBC drivers.
>
> Even after you’re connected to the cluster from JDBC or ODBC side you’re
> no longer limited by distributed SQL queries. You can freely and easily
> modify the data with INSERT, UPDATE and DELETE statements thanks to
> comprehensive DML supported contributed by Alexander Paschenko in version
> 1.8.  To prove this, Igor Sapego issued a guide <
> https://apacheignite.readme.io/docs/pdo-interoperability> on how to start
> working with an Ignite cluster from PHP side which doesn’t have its own API
> implementation on Ignite side.
>
> At all, all this means that SQL features set deserved its own component
> which I propose to call In-Memory SQL Grid to conform the naming of the
> rest of big components like Data Grid, Compute Grid, Service Grid.
>
> I’ve already started reworking our documentation and will spend some time
> by enriching and expanding it. However, this is a starting point:
> https://apacheignite.readme.io/docs/sql-grid  io/docs/sql-grid>
>
> Feel free to share your thoughts regarding the naming or content of the
> doc in general.
>
> —
> Denis
>
> [1] https://apacheignite.readme.io/docs/sql-grid

Re: Storing deserialized value when indexing is enabled

[Denis Magda]

Val,

Yeah, the code is like jungles in some places. Proposed a possible fix inside 
of the ticket.

—
Denis

> On Nov 23, 2016, at 1:01 PM, Valentin Kulichenko 
>  wrote:
> 
> Denis,
> 
> CacheObjectBinaryProcessorImpl calls super and preserves the value of
> storeVal flag. It seems to me that it's then used in
> BinaryObjectImpl.deserializeValue() causing the deserialized value to be
> saved in memory. This doubles memory consumption in this scenario.
> 
> I created a ticket: https://issues.apache.org/jira/browse/IGNITE-4293
> 
> -Val
> 
> On Wed, Nov 23, 2016 at 12:32 PM, Denis Magda  wrote:
> 
>> Val,
>> 
>> You get confused by IgniteCacheObjectProcessorImpl.contextForCache(…)
>> method.
>> 
>> When binary marshaller is enable the default processor is
>> CacheObjectBinaryProcessorImpl and when contextForCache(…) gets called on
>> its side the processor will create CacheObjectBinaryContext which, in its
>> turn, has binaryEnabled field that in fact controls an object
>> deserialization on a server side.
>> 
>> —
>> Denis
>> 
>>> On Nov 23, 2016, at 12:14 PM, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>>> 
>>> Folks,
>>> 
>>> It looks like we cache the deserialized value in case indexing is enabled
>>> and a read operation happens on server side (e.g. affinity closure does
>>> get() on primary node).
>>> 
>>> This must be caused by this piece of code in
>> IgniteCacheObjectProcessorImpl:
>>> 
>>> boolean storeVal = ctx.config().isPeerClassLoadingEnabled() ||
>>>   GridQueryProcessor.isEnabled(ccfg) ||
>>>   !ccfg.isCopyOnRead();
>>> 
>>> This actually means that we store deserialized values in case indexing is
>>> configured even if copyOnRead is true. My understanding is that this is a
>>> bug and GridQueryProcessor.isEnabled(ccfg) condition should be removed
>> from
>>> there (at least for the case when binary marshaller is used).
>>> 
>>> Am I missing something?
>>> 
>>> -Val
>> 
>> 

FOSDEM 2017 HPC, Bigdata and Data Science DevRoom CFP is closing soon

[Roman Shaposhnik]

Hi!

apologies for the extra wide distribution (this exhausts my once
a year ASF mail-to-all-bigdata-projects quota ;-)) but I wanted
to suggest that all of you should consider submitting talks
to FOSDEM 2017 HPC, Bigdata and Data Science DevRoom:
https://hpc-bigdata-fosdem17.github.io/

It was a great success this year and we hope to make it an even
bigger success in 2017.

Besides -- FOSDEM is the biggest gathering of open source
developers on the face of the earth -- don't miss it!

Thanks,
Roman.

P.S. If you have any questions -- please email me directly and
see you all in Brussels!

Re: Start contributing

[Denis Magda]

Hi Maks,

Welcome to the Ignite community!

You should get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Once you got familiar and were able to run a few examples, you should pick
a Jira ticket you would like to start on. Send an email to the dev list, so
we can add you as a contributor in Jira.

You can find interesting tickets to get started here:
https://ignite.apache.org/community/contribute.html#pick-ticket

Looking forward to your contributions!

Regards,
Denis

> On Nov 23, 2016, at 1:36 AM, Максим Козлов  wrote:
> 
> Hello
> 
> -- 
> Best regards, Maks Kozlov

Re: Hello

[Denis Magda]

Here are some ticket you may want to start with
https://ignite.apache.org/community/contribute.html#pick-ticket 


—
Denis

> On Nov 23, 2016, at 5:33 AM, Dmitriy Setrakyan  wrote:
> 
> Hi Alex,
> 
> Welcome to the Ignite community!
> 
> Once you are familiar with the contribution process, please see if there is
> a specific Jira ticket you would like work on. We will help you get started.
> 
> D.
> 
> On Wed, Nov 23, 2016 at 2:24 AM, Vladislav Pyatkov 
> wrote:
> 
>> Please read https://ignite.apache.org/community/contribute.html#contribute
>> 
>> Looking forward for your contributions!
>> 
>> On Wed, Nov 23, 2016 at 1:15 PM, Александр Меньшиков >> 
>> wrote:
>> 
>>> I want to contribute.
>>> 
>>> 2016-11-23 13:04 GMT+03:00 Vladislav Pyatkov :
>>> 
 Hi Alex,
 
 This is Apache Ignite development community.
 Are you want to contribute to Ignite or you are have any suggestion?
 
 On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков <
 sharple...@gmail.com>
 wrote:
 
> Hello
> 
 
>>> 
>> 

[jira] [Created] (IGNITE-4293) Deserialized value is cached if queries are enabled

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-4293:
---

 Summary: Deserialized value is cached if queries are enabled
 Key: IGNITE-4293
 URL: https://issues.apache.org/jira/browse/IGNITE-4293
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.7
Reporter: Valentin Kulichenko
Priority: Critical


Here is the problematic piece of code in {{IgniteCacheObjectProcessorImpl}}:
{code}
boolean storeVal = ctx.config().isPeerClassLoadingEnabled() ||
GridQueryProcessor.isEnabled(ccfg) ||
!ccfg.isCopyOnRead();
{code}
This flag is set to true if queries are enabled even when binary marshaller is 
used (this condition makes sense to other marshallers though). It is then use 
in {{BinaryObjectImpl.deserializeValue}}:
{code}
if (coCtx != null && coCtx.storeValue())
obj = obj0;
{code}
As a result, memory consumption doubles.



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

Re: Storing deserialized value when indexing is enabled

[Valentin Kulichenko]

Denis,

CacheObjectBinaryProcessorImpl calls super and preserves the value of
storeVal flag. It seems to me that it's then used in
BinaryObjectImpl.deserializeValue() causing the deserialized value to be
saved in memory. This doubles memory consumption in this scenario.

I created a ticket: https://issues.apache.org/jira/browse/IGNITE-4293

-Val

On Wed, Nov 23, 2016 at 12:32 PM, Denis Magda  wrote:

> Val,
>
> You get confused by IgniteCacheObjectProcessorImpl.contextForCache(…)
> method.
>
> When binary marshaller is enable the default processor is
> CacheObjectBinaryProcessorImpl and when contextForCache(…) gets called on
> its side the processor will create CacheObjectBinaryContext which, in its
> turn, has binaryEnabled field that in fact controls an object
> deserialization on a server side.
>
> —
> Denis
>
> > On Nov 23, 2016, at 12:14 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
> >
> > Folks,
> >
> > It looks like we cache the deserialized value in case indexing is enabled
> > and a read operation happens on server side (e.g. affinity closure does
> > get() on primary node).
> >
> > This must be caused by this piece of code in
> IgniteCacheObjectProcessorImpl:
> >
> > boolean storeVal = ctx.config().isPeerClassLoadingEnabled() ||
> >GridQueryProcessor.isEnabled(ccfg) ||
> >!ccfg.isCopyOnRead();
> >
> > This actually means that we store deserialized values in case indexing is
> > configured even if copyOnRead is true. My understanding is that this is a
> > bug and GridQueryProcessor.isEnabled(ccfg) condition should be removed
> from
> > there (at least for the case when binary marshaller is used).
> >
> > Am I missing something?
> >
> > -Val
>
>

Apache Ignite Contribution: Kubernetes, Streaming, Data Structures and More

[Denis Magda]

Guys,

If someone of you locates in the U.S. and doesn’t know how to spend upcoming 
holidays effectively I would remind that Ignite might make this days more 
colorful and memorable. What you need to do is to pick up a ticket of interest 
and contribute it to the project.
https://ignite.apache.org/community/contribute.html#pick-ticket 


Among the tickets we have tasks related to the integration with Kubernetes and 
variety of streamers. Even more you can improve your algorithmic skills by 
implementing one of distributed data structures that is missing in Ignite. If 
you’re experienced in Spark and Python then you can help out to provide Ignite 
RDDs integration for Spark. In any case you’ll definitely will find work of 
interest ;)

—
Denis

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

[Rohit Gupta]

Thank you, Val! I will follow your suggestion.

Rohit

On Wed, Nov 23, 2016 at 10:22 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rohit,
>
> If you unsubscribe, your messages will not be redirected to the list what
> you post on Nabble, which means that majority of community members will not
> read them. I recommend you to just filter out emails you don't need.
>
> -Val
>
> On Wed, Nov 23, 2016 at 10:12 AM, Pavel Tupitsyn 
> wrote:
>
> > I'll be fun to be able to subscribe and unsubscribe other people :)
> > But it is not possible.
> >
> > See http://apache.org/foundation/mailinglists.html
> >
> > On Wed, Nov 23, 2016 at 9:02 PM, Rohit Gupta 
> > wrote:
> >
> > > Thank you, Pavel! Can you please unsubscribe me from the emails?
> > >
> > > Thanks,
> > >
> > > Rohit
> > >
> > > On Wed, Nov 23, 2016 at 9:52 AM, Pavel Tupitsyn 
> > > wrote:
> > >
> > > > Hi, yes, you can use online mail archives:
> > > > http://apache-ignite-developers.2346864.n4.nabble.com/
> > > >
> > > > On Wed, Nov 23, 2016 at 8:48 PM, Rohit Gupta  >
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I am sorry to bother you. I am wondering if I can follow the
> > discussion
> > > > > online without getting emails. Please let me know.
> > > > >
> > > > > Thank you!
> > > > > Sincerely,
> > > > > Rohit
> > > > >
> > > > > On Wed, Nov 23, 2016 at 9:34 AM, Pavel Tupitsyn (JIRA) <
> > > j...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Pavel Tupitsyn created IGNITE-4292:
> > > > > > --
> > > > > >
> > > > > >  Summary: SQL: Except returns incorrect results
> > > > > >  Key: IGNITE-4292
> > > > > >  URL: https://issues.apache.org/
> > > > jira/browse/IGNITE-4292
> > > > > >  Project: Ignite
> > > > > >   Issue Type: Bug
> > > > > >   Components: SQL
> > > > > > Affects Versions: 1.8
> > > > > > Reporter: Pavel Tupitsyn
> > > > > >  Fix For: 1.8
> > > > > >
> > > > > >
> > > > > > {code}
> > > > > > select _T0._key from "".Person as _T0 except (select _T1._foo
> from
> > > > > > "role_cache".Role as _T1)
> > > > > > {code}
> > > > > >
> > > > > > Returns all keys even though some are present in both tables.
> > > > > >
> > > > > > This is CacheLinqTest.TestExcept in "Ignite Platform .NET" suite.
> > > Works
> > > > > in
> > > > > > master, does not work in ignite-1.8 after DML merge.
> > > > > >
> > > > > > Models:
> > > > > > {code}
> > > > > > CREATE MEMORY TABLE "".PERSON(
> > > > > > _KEY INT NOT NULL,
> > > > > > _VAL OTHER,
> > > > > > AGE1 INT,
> > > > > > NAME VARCHAR,
> > > > > > ADDRESS OTHER,
> > > > > > ZIP INT,
> > > > > > STREET VARCHAR,
> > > > > > ADDR_ALIASTEST INT,
> > > > > > ORGANIZATIONID INT,
> > > > > > BIRTHDAY TIMESTAMP,
> > > > > > PERSON_ALIASTEST INT
> > > > > > )
> > > > > >
> > > > > > CREATE MEMORY TABLE "role_cache".ROLE(
> > > > > > _KEY OTHER NOT NULL,
> > > > > > _VAL OTHER,
> > > > > > _FOO INT,
> > > > > > _BAR BIGINT,
> > > > > > NAME VARCHAR,
> > > > > > DATE TIMESTAMP
> > > > > > )
> > > > > >
> > > > > > CREATE MEMORY TABLE "person_cache".PERSON(
> > > > > > _KEY INT NOT NULL,
> > > > > > _VAL OTHER,
> > > > > > AGE1 INT,
> > > > > > NAME VARCHAR,
> > > > > > ADDRESS OTHER,
> > > > > > ZIP INT,
> > > > > > STREET VARCHAR,
> > > > > > ALIASTEST INT,
> > > > > > ORGANIZATIONID INT,
> > > > > > BIRTHDAY TIMESTAMP
> > > > > > )
> > > > > > {code}
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > This message was sent by Atlassian JIRA
> > > > > > (v6.3.4#6332)
> > > > > >
> > > > >
> > > >
> > >
> >
>

Storing deserialized value when indexing is enabled

[Valentin Kulichenko]

Folks,

It looks like we cache the deserialized value in case indexing is enabled
and a read operation happens on server side (e.g. affinity closure does
get() on primary node).

This must be caused by this piece of code in IgniteCacheObjectProcessorImpl:

boolean storeVal = ctx.config().isPeerClassLoadingEnabled() ||
GridQueryProcessor.isEnabled(ccfg) ||
!ccfg.isCopyOnRead();

This actually means that we store deserialized values in case indexing is
configured even if copyOnRead is true. My understanding is that this is a
bug and GridQueryProcessor.isEnabled(ccfg) condition should be removed from
there (at least for the case when binary marshaller is used).

Am I missing something?

-Val

In-Memory SQL Grid

[Denis Magda]

Community,

Frankly speaking, Ignite’s SQL support goes far beyond the notion of Data Grid 
starting from Apache Ignite 1.8.
SQL in Ignite is no longer about distributed ANSI-99 SELECT queries only.

It will be about the ability to connect to an Ignite Cluster not only from 
Java, .NET and C++ sides, that have their own SQL APIs, but, in general, from 
your favorite programming language or analytical tool by the usage of Ignite’s 
JDBC and ODBC drivers. 

Even after you’re connected to the cluster from JDBC or ODBC side you’re no 
longer limited by distributed SQL queries. You can freely and easily modify the 
data with INSERT, UPDATE and DELETE statements thanks to comprehensive DML 
supported contributed by Alexander Paschenko in version 1.8.  To prove this, 
Igor Sapego issued a guide 
 on how to start 
working with an Ignite cluster from PHP side which doesn’t have its own API 
implementation on Ignite side.

At all, all this means that SQL features set deserved its own component which I 
propose to call In-Memory SQL Grid to conform the naming of the rest of big 
components like Data Grid, Compute Grid, Service Grid.

I’ve already started reworking our documentation and will spend some time by 
enriching and expanding it. However, this is a starting point:
https://apacheignite.readme.io/docs/sql-grid 


Feel free to share your thoughts regarding the naming or content of the doc in 
general.

—
Denis

[1] https://apacheignite.readme.io/docs/sql-grid

SparkRDD with Ignite

[Vidhya Gurumoorthi (vgurumoo)]

Have been extensively trying to integrate spark rdd's with ignite. We have 
spark version 1.6.1 with apache-ignite-1.6.0-src. Tried out the example in 
"https://apacheignite-fs.readme.io/docs/testing-integration-with-spark-shell​; 
and it is working fine. However, all efforts w.r.t connecting to spark 
dataframes/rdd's have been fruitless. Have listed the steps below, Any inputs 
on what is missing will be of great help. We have a 10 node spark-hadoop 
cluster.  Please suggest if there are any other better approach than converting 
df's to rdd's and using ignite saveValues ?


1.  val df2 = sqlContext.read.jdbc(url, "SAMPLE_DATA", props)​ // Dataframe 
that reads Oracle SAMPLE_DATA table.

df2.show() returns all the values in table. We are good from spark perspective 
at this point.


2.

import org.apache.spark.rdd.RDD

import org.apache.spark.sql.Row

val rows: RDD[Row] = df2.rdd // Converting dataframe to rdd's


Setting up ignite properties:


1. scala> import org.apache.ignite.spark._

2. scala> import org.apache.ignite.configuration._​

3. val igniteContext = new 
IgniteContext[org.apache.spark.sql.Row,org.apache.spark.sql.Row](sc, () => new 
IgniteConfiguration())

4. val sharedRDD = igniteContext.fromCache("partitioned")​

5. sharedRDD.saveValues(rows: RDD[Row])


After this, hitting the below error..


scala> sharedRDD.saveValues(rows: RDD[Row])

16/11/23 13:23:57 WARN TaskSetManager: Lost task 0.0 in stage 0.0 (TID 0, 
xxx006.xxx.com): java.lang.IllegalStateException: Did not find registered 
driver with class oracle.jdbc.OracleDriver

at 
org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$$anonfun$createConnectionFactory$2$$anonfun$3.apply(JdbcUtils.scala:58)

at 
org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$$anonfun$createConnectionFactory$2$$anonfun$3.apply(JdbcUtils.scala:58)

at scala.Option.getOrElse(Option.scala:120)

at 
org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$$anonfun$createConnectionFactory$2.apply(JdbcUtils.scala:57)

at 
org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$$anonfun$createConnectionFactory$2.apply(JdbcUtils.scala:52)

at 
org.apache.spark.sql.execution.datasources.jdbc.JDBCRDD$$anon$1.(JDBCRDD.scala:347)

at 
org.apache.spark.sql.execution.datasources.jdbc.JDBCRDD.compute(JDBCRDD.scala:339)

at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:306)

at org.apache.spark.rdd.RDD.iterator(RDD.scala:270)

at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)

at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:306)

at org.apache.spark.rdd.RDD.iterator(RDD.scala:270)

at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:66)

at org.apache.spark.scheduler.Task.run(Task.scala:89)

at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:214)

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)


[13:24:00] Topology snapshot [ver=28, servers=3, clients=1, CPUs=16, heap=4.0GB]

16/11/23 13:24:01 WARN TaskSetManager: Lost task 0.1 in stage 0.0 (TID 1, 
xxx001): java.lang.NoSuchMethodError: 
scala.Predef$.$conforms()Lscala/Predef$$less$colon$less;

at 
org.apache.ignite.spark.IgniteRDD$$anonfun$saveValues$1$$anonfun$apply$1.apply(IgniteRDD.scala:151)

at 
org.apache.ignite.spark.IgniteRDD$$anonfun$saveValues$1$$anonfun$apply$1.apply(IgniteRDD.scala:150)

at scala.collection.Iterator$class.foreach(Iterator.scala:727)

at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)

at 
org.apache.ignite.spark.IgniteRDD$$anonfun$saveValues$1.apply(IgniteRDD.scala:150)

at 
org.apache.ignite.spark.IgniteRDD$$anonfun$saveValues$1.apply(IgniteRDD.scala:138)

at 
org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1$$anonfun$apply$33.apply(RDD.scala:920)

at 
org.apache.spark.rdd.RDD$$anonfun$foreachPartition$1$$anonfun$apply$33.apply(RDD.scala:920)

at 
org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:1858)

at 
org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:1858)

at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:66)

at org.apache.spark.scheduler.Task.run(Task.scala:89)

at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:214)

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)


[13:24:01] Topology snapshot [ver=29, servers=2, clients=1, CPUs=16, heap=3.0GB]

16/11/23 13:24:02 ERROR TaskSchedulerImpl: Lost executor 3 on xxx001: Remote 
RPC client disassociated. Likely due to containers exceeding thresholds, or 
network issues. Check driver logs for WARN messages.


16/11/23 13:24:05 ERROR TaskSetManager: Task 0 in stage 0.0 failed 4 times; 
aborting job

Blogging about new .NET features

[Denis Magda]

Pavel,

Do you mind blogging about ASP.NET session state [1] and Entity Framework 2nd 
level cache [2] support after 1.8 release goes public?

Also I would remind everyone in the community that it’s always welcomed to 
share your experience or Ignite related news over blog posts. We track all the 
posts on this page.
https://ignite.apache.org/blogs.html 


[1] https://apacheignite-net.readme.io/docs/aspnet-session-state-caching 

[2] https://apacheignite-net.readme.io/docs/entity-framework-second-level-cache 


—
Denis

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

[Valentin Kulichenko]

Hi Rohit,

If you unsubscribe, your messages will not be redirected to the list what
you post on Nabble, which means that majority of community members will not
read them. I recommend you to just filter out emails you don't need.

-Val

On Wed, Nov 23, 2016 at 10:12 AM, Pavel Tupitsyn 
wrote:

> I'll be fun to be able to subscribe and unsubscribe other people :)
> But it is not possible.
>
> See http://apache.org/foundation/mailinglists.html
>
> On Wed, Nov 23, 2016 at 9:02 PM, Rohit Gupta 
> wrote:
>
> > Thank you, Pavel! Can you please unsubscribe me from the emails?
> >
> > Thanks,
> >
> > Rohit
> >
> > On Wed, Nov 23, 2016 at 9:52 AM, Pavel Tupitsyn 
> > wrote:
> >
> > > Hi, yes, you can use online mail archives:
> > > http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> > > On Wed, Nov 23, 2016 at 8:48 PM, Rohit Gupta 
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > I am sorry to bother you. I am wondering if I can follow the
> discussion
> > > > online without getting emails. Please let me know.
> > > >
> > > > Thank you!
> > > > Sincerely,
> > > > Rohit
> > > >
> > > > On Wed, Nov 23, 2016 at 9:34 AM, Pavel Tupitsyn (JIRA) <
> > j...@apache.org>
> > > > wrote:
> > > >
> > > > > Pavel Tupitsyn created IGNITE-4292:
> > > > > --
> > > > >
> > > > >  Summary: SQL: Except returns incorrect results
> > > > >  Key: IGNITE-4292
> > > > >  URL: https://issues.apache.org/
> > > jira/browse/IGNITE-4292
> > > > >  Project: Ignite
> > > > >   Issue Type: Bug
> > > > >   Components: SQL
> > > > > Affects Versions: 1.8
> > > > > Reporter: Pavel Tupitsyn
> > > > >  Fix For: 1.8
> > > > >
> > > > >
> > > > > {code}
> > > > > select _T0._key from "".Person as _T0 except (select _T1._foo from
> > > > > "role_cache".Role as _T1)
> > > > > {code}
> > > > >
> > > > > Returns all keys even though some are present in both tables.
> > > > >
> > > > > This is CacheLinqTest.TestExcept in "Ignite Platform .NET" suite.
> > Works
> > > > in
> > > > > master, does not work in ignite-1.8 after DML merge.
> > > > >
> > > > > Models:
> > > > > {code}
> > > > > CREATE MEMORY TABLE "".PERSON(
> > > > > _KEY INT NOT NULL,
> > > > > _VAL OTHER,
> > > > > AGE1 INT,
> > > > > NAME VARCHAR,
> > > > > ADDRESS OTHER,
> > > > > ZIP INT,
> > > > > STREET VARCHAR,
> > > > > ADDR_ALIASTEST INT,
> > > > > ORGANIZATIONID INT,
> > > > > BIRTHDAY TIMESTAMP,
> > > > > PERSON_ALIASTEST INT
> > > > > )
> > > > >
> > > > > CREATE MEMORY TABLE "role_cache".ROLE(
> > > > > _KEY OTHER NOT NULL,
> > > > > _VAL OTHER,
> > > > > _FOO INT,
> > > > > _BAR BIGINT,
> > > > > NAME VARCHAR,
> > > > > DATE TIMESTAMP
> > > > > )
> > > > >
> > > > > CREATE MEMORY TABLE "person_cache".PERSON(
> > > > > _KEY INT NOT NULL,
> > > > > _VAL OTHER,
> > > > > AGE1 INT,
> > > > > NAME VARCHAR,
> > > > > ADDRESS OTHER,
> > > > > ZIP INT,
> > > > > STREET VARCHAR,
> > > > > ALIASTEST INT,
> > > > > ORGANIZATIONID INT,
> > > > > BIRTHDAY TIMESTAMP
> > > > > )
> > > > > {code}
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > This message was sent by Atlassian JIRA
> > > > > (v6.3.4#6332)
> > > > >
> > > >
> > >
> >
>

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

[Rohit Gupta]

Thank you, Pavel! Can you please unsubscribe me from the emails?

Thanks,

Rohit

On Wed, Nov 23, 2016 at 9:52 AM, Pavel Tupitsyn 
wrote:

> Hi, yes, you can use online mail archives:
> http://apache-ignite-developers.2346864.n4.nabble.com/
>
> On Wed, Nov 23, 2016 at 8:48 PM, Rohit Gupta 
> wrote:
>
> > Hello,
> >
> > I am sorry to bother you. I am wondering if I can follow the discussion
> > online without getting emails. Please let me know.
> >
> > Thank you!
> > Sincerely,
> > Rohit
> >
> > On Wed, Nov 23, 2016 at 9:34 AM, Pavel Tupitsyn (JIRA) 
> > wrote:
> >
> > > Pavel Tupitsyn created IGNITE-4292:
> > > --
> > >
> > >  Summary: SQL: Except returns incorrect results
> > >  Key: IGNITE-4292
> > >  URL: https://issues.apache.org/
> jira/browse/IGNITE-4292
> > >  Project: Ignite
> > >   Issue Type: Bug
> > >   Components: SQL
> > > Affects Versions: 1.8
> > > Reporter: Pavel Tupitsyn
> > >  Fix For: 1.8
> > >
> > >
> > > {code}
> > > select _T0._key from "".Person as _T0 except (select _T1._foo from
> > > "role_cache".Role as _T1)
> > > {code}
> > >
> > > Returns all keys even though some are present in both tables.
> > >
> > > This is CacheLinqTest.TestExcept in "Ignite Platform .NET" suite. Works
> > in
> > > master, does not work in ignite-1.8 after DML merge.
> > >
> > > Models:
> > > {code}
> > > CREATE MEMORY TABLE "".PERSON(
> > > _KEY INT NOT NULL,
> > > _VAL OTHER,
> > > AGE1 INT,
> > > NAME VARCHAR,
> > > ADDRESS OTHER,
> > > ZIP INT,
> > > STREET VARCHAR,
> > > ADDR_ALIASTEST INT,
> > > ORGANIZATIONID INT,
> > > BIRTHDAY TIMESTAMP,
> > > PERSON_ALIASTEST INT
> > > )
> > >
> > > CREATE MEMORY TABLE "role_cache".ROLE(
> > > _KEY OTHER NOT NULL,
> > > _VAL OTHER,
> > > _FOO INT,
> > > _BAR BIGINT,
> > > NAME VARCHAR,
> > > DATE TIMESTAMP
> > > )
> > >
> > > CREATE MEMORY TABLE "person_cache".PERSON(
> > > _KEY INT NOT NULL,
> > > _VAL OTHER,
> > > AGE1 INT,
> > > NAME VARCHAR,
> > > ADDRESS OTHER,
> > > ZIP INT,
> > > STREET VARCHAR,
> > > ALIASTEST INT,
> > > ORGANIZATIONID INT,
> > > BIRTHDAY TIMESTAMP
> > > )
> > > {code}
> > >
> > >
> > >
> > > --
> > > This message was sent by Atlassian JIRA
> > > (v6.3.4#6332)
> > >
> >
>

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

[Pavel Tupitsyn]

Hi, yes, you can use online mail archives:
http://apache-ignite-developers.2346864.n4.nabble.com/

On Wed, Nov 23, 2016 at 8:48 PM, Rohit Gupta  wrote:

> Hello,
>
> I am sorry to bother you. I am wondering if I can follow the discussion
> online without getting emails. Please let me know.
>
> Thank you!
> Sincerely,
> Rohit
>
> On Wed, Nov 23, 2016 at 9:34 AM, Pavel Tupitsyn (JIRA) 
> wrote:
>
> > Pavel Tupitsyn created IGNITE-4292:
> > --
> >
> >  Summary: SQL: Except returns incorrect results
> >  Key: IGNITE-4292
> >  URL: https://issues.apache.org/jira/browse/IGNITE-4292
> >  Project: Ignite
> >   Issue Type: Bug
> >   Components: SQL
> > Affects Versions: 1.8
> > Reporter: Pavel Tupitsyn
> >  Fix For: 1.8
> >
> >
> > {code}
> > select _T0._key from "".Person as _T0 except (select _T1._foo from
> > "role_cache".Role as _T1)
> > {code}
> >
> > Returns all keys even though some are present in both tables.
> >
> > This is CacheLinqTest.TestExcept in "Ignite Platform .NET" suite. Works
> in
> > master, does not work in ignite-1.8 after DML merge.
> >
> > Models:
> > {code}
> > CREATE MEMORY TABLE "".PERSON(
> > _KEY INT NOT NULL,
> > _VAL OTHER,
> > AGE1 INT,
> > NAME VARCHAR,
> > ADDRESS OTHER,
> > ZIP INT,
> > STREET VARCHAR,
> > ADDR_ALIASTEST INT,
> > ORGANIZATIONID INT,
> > BIRTHDAY TIMESTAMP,
> > PERSON_ALIASTEST INT
> > )
> >
> > CREATE MEMORY TABLE "role_cache".ROLE(
> > _KEY OTHER NOT NULL,
> > _VAL OTHER,
> > _FOO INT,
> > _BAR BIGINT,
> > NAME VARCHAR,
> > DATE TIMESTAMP
> > )
> >
> > CREATE MEMORY TABLE "person_cache".PERSON(
> > _KEY INT NOT NULL,
> > _VAL OTHER,
> > AGE1 INT,
> > NAME VARCHAR,
> > ADDRESS OTHER,
> > ZIP INT,
> > STREET VARCHAR,
> > ALIASTEST INT,
> > ORGANIZATIONID INT,
> > BIRTHDAY TIMESTAMP
> > )
> > {code}
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
> >
>

Re: [jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

[Rohit Gupta]

Hello,

I am sorry to bother you. I am wondering if I can follow the discussion
online without getting emails. Please let me know.

Thank you!
Sincerely,
Rohit

On Wed, Nov 23, 2016 at 9:34 AM, Pavel Tupitsyn (JIRA) 
wrote:

> Pavel Tupitsyn created IGNITE-4292:
> --
>
>  Summary: SQL: Except returns incorrect results
>  Key: IGNITE-4292
>  URL: https://issues.apache.org/jira/browse/IGNITE-4292
>  Project: Ignite
>   Issue Type: Bug
>   Components: SQL
> Affects Versions: 1.8
> Reporter: Pavel Tupitsyn
>  Fix For: 1.8
>
>
> {code}
> select _T0._key from "".Person as _T0 except (select _T1._foo from
> "role_cache".Role as _T1)
> {code}
>
> Returns all keys even though some are present in both tables.
>
> This is CacheLinqTest.TestExcept in "Ignite Platform .NET" suite. Works in
> master, does not work in ignite-1.8 after DML merge.
>
> Models:
> {code}
> CREATE MEMORY TABLE "".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ADDR_ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP,
> PERSON_ALIASTEST INT
> )
>
> CREATE MEMORY TABLE "role_cache".ROLE(
> _KEY OTHER NOT NULL,
> _VAL OTHER,
> _FOO INT,
> _BAR BIGINT,
> NAME VARCHAR,
> DATE TIMESTAMP
> )
>
> CREATE MEMORY TABLE "person_cache".PERSON(
> _KEY INT NOT NULL,
> _VAL OTHER,
> AGE1 INT,
> NAME VARCHAR,
> ADDRESS OTHER,
> ZIP INT,
> STREET VARCHAR,
> ALIASTEST INT,
> ORGANIZATIONID INT,
> BIRTHDAY TIMESTAMP
> )
> {code}
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

[jira] [Created] (IGNITE-4292) SQL: Except returns incorrect results

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4292:
--

 Summary: SQL: Except returns incorrect results
 Key: IGNITE-4292
 URL: https://issues.apache.org/jira/browse/IGNITE-4292
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
 Fix For: 1.8


{code}
select _T0._key from "".Person as _T0 except (select _T1._foo from 
"role_cache".Role as _T1)
{code}

Returns all keys even though some are present in both tables.

This is CacheLinqTest.TestExcept in "Ignite Platform .NET" suite. Works in 
master, does not work in ignite-1.8 after DML merge.

Models:
{code}
CREATE MEMORY TABLE "".PERSON(
_KEY INT NOT NULL,
_VAL OTHER,
AGE1 INT,
NAME VARCHAR,
ADDRESS OTHER,
ZIP INT,
STREET VARCHAR,
ADDR_ALIASTEST INT,
ORGANIZATIONID INT,
BIRTHDAY TIMESTAMP,
PERSON_ALIASTEST INT
)

CREATE MEMORY TABLE "role_cache".ROLE(
_KEY OTHER NOT NULL,
_VAL OTHER,
_FOO INT,
_BAR BIGINT,
NAME VARCHAR,
DATE TIMESTAMP
)

CREATE MEMORY TABLE "person_cache".PERSON(
_KEY INT NOT NULL,
_VAL OTHER,
AGE1 INT,
NAME VARCHAR,
ADDRESS OTHER,
ZIP INT,
STREET VARCHAR,
ALIASTEST INT,
ORGANIZATIONID INT,
BIRTHDAY TIMESTAMP
)
{code}



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

[jira] [Created] (IGNITE-4291) SQL: Multi-from join returns no results

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4291:
--

 Summary: SQL: Multi-from join returns no results
 Key: IGNITE-4291
 URL: https://issues.apache.org/jira/browse/IGNITE-4291
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
 Fix For: 1.8


{code}
 select _T0.Name, _T1.Name from "".Person as _T0 , "role_cache".Role as _T1 
where (_T0._key < ?) and (_T0._key = _T1._foo)
{code}

This is CacheLinqTest.TestMultipleFrom in "Ignite Platform .NET" suite. Works 
in master, does not work in ignite-1.8 after DML merge.

Models:
{code}
CREATE MEMORY TABLE "".PERSON(
_KEY INT NOT NULL,
_VAL OTHER,
AGE1 INT,
NAME VARCHAR,
ADDRESS OTHER,
ZIP INT,
STREET VARCHAR,
ADDR_ALIASTEST INT,
ORGANIZATIONID INT,
BIRTHDAY TIMESTAMP,
PERSON_ALIASTEST INT
)

CREATE MEMORY TABLE "role_cache".ROLE(
_KEY OTHER NOT NULL,
_VAL OTHER,
_FOO INT,
_BAR BIGINT,
NAME VARCHAR,
DATE TIMESTAMP
)

CREATE MEMORY TABLE "person_cache".PERSON(
_KEY INT NOT NULL,
_VAL OTHER,
AGE1 INT,
NAME VARCHAR,
ADDRESS OTHER,
ZIP INT,
STREET VARCHAR,
ALIASTEST INT,
ORGANIZATIONID INT,
BIRTHDAY TIMESTAMP
)
{code}



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

[jira] [Created] (IGNITE-4290) SQL: Three-way join returns no results

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4290:
--

 Summary: SQL: Three-way join returns no results
 Key: IGNITE-4290
 URL: https://issues.apache.org/jira/browse/IGNITE-4290
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
 Fix For: 1.8


Join three tables (two from the same cache) - no results returned.

{code}
 select _T0._key, _T0._val, _T1._key, _T1._val, _T2._key, _T2._val from 
"role_cache".Role as _T2 inner join "".Person as _T1 on (_T1._key = _T2._foo) 
inner join "".Organization as _T0 on (_T0.Id = _T1.OrganizationId)
{code}

This is CacheLinqTest.TestMulticacheJoin in "Ignite Platform .NET" suite. Works 
in master, does not work in ignite-1.8 after DML merge.

Models:
{code}
CREATE MEMORY TABLE "".PERSON(
_KEY INT NOT NULL,
_VAL OTHER,
AGE1 INT,
NAME VARCHAR,
ADDRESS OTHER,
ZIP INT,
STREET VARCHAR,
ADDR_ALIASTEST INT,
ORGANIZATIONID INT,
BIRTHDAY TIMESTAMP,
PERSON_ALIASTEST INT
)

CREATE MEMORY TABLE "role_cache".ROLE(
_KEY OTHER NOT NULL,
_VAL OTHER,
_FOO INT,
_BAR BIGINT,
NAME VARCHAR,
DATE TIMESTAMP
)

CREATE MEMORY TABLE "person_cache".PERSON(
_KEY INT NOT NULL,
_VAL OTHER,
AGE1 INT,
NAME VARCHAR,
ADDRESS OTHER,
ZIP INT,
STREET VARCHAR,
ALIASTEST INT,
ORGANIZATIONID INT,
BIRTHDAY TIMESTAMP
)
{code}



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

Re: Apache Ignite 1.8 Release

[Igor Sapego]

Denis,

I've raised PRs and Vladimir has merged them into ignite-1.8. But now we
have some
failing ODBC tests in the branch. I'm currently working on them. There is a
ticket for
that which you can track [1]. I'll add all my findings there.

[1] https://issues.apache.org/jira/browse/IGNITE-4288

Best Regards,
Igor

On Wed, Nov 23, 2016 at 7:08 PM, Denis Magda  wrote:

> Alexander,
>
> Awesome news, thanks for making this happen!
>
> Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I start
> testing that PHP-PDO guidance [1] is correct?
>
> [1] https://apacheignite.readme.io/docs/pdo-interoperability <
> https://apacheignite.readme.io/docs/pdo-interoperability>
>
> —
> Denis
>
> > On Nov 23, 2016, at 12:01 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
> >
> > Folks,
> >
> > Yesterday it'd been agreed with Sergi that DML branch is now good to
> > be included into 1.8 branch that is to be created.
> >
> > Minor review fixes, should they be made, and test fixes will be
> > incorporated into 1.8 as separate patches later.
> >
> > Also, it'd been agreed that, in order to deliver these new features on
> > time, two subtasks will be fixed in later releases (shortly):
> >
> > https://issues.apache.org/jira/browse/IGNITE-4268
> > https://issues.apache.org/jira/browse/IGNITE-4269
> >
> > On failing tests:
> > https://issues.apache.org/jira/browse/IGNITE-2294?
> focusedCommentId=15683377
> >
> > - Alex
> >
> > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > :
> >> Vlad,
> >>
> >> Most likely today.
> >>
> >> - Alex
> >>
> >> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> >>> Igniters,
> >>>
> >>> I went through remaining tickets assigned to 1.8 and it seems that we
> are
> >>> pretty close to release. As far as I understand the biggest remaining
> >>> feature is DML [1]. I think we can create separate branch for 1.8 as
> soon
> >>> as it is merged. Alex, do you have any idea on when it might happen?
> >>>
> >>> Vladimir.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> >>>
> >>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
> wrote:
> >>>
>  Roman,
> 
>  That versions will be created after 1.8 gets released. Recently there
> was
>  a discussion on the dev list [1] regarding the difficulties related to
>  documentation maintenance when several documentation versions
> co-exist at
>  the same time.
> 
>  It was decided that rather then create a new version for the
> documentation
>  once a new feature added to Ignite it’s better to create a hidden page
>  under the current documentation version and make it visible once the
> next
>  version is created after the release.
> 
>  The bottom line is that, please create a hidden page with a suffix
>  “page_name-1.8” and once 1.8 gets released Prachi will create
> readme.io <
>  http://readme.io/> 1.8 and make your doc visible.
> 
>  [1] http://apache-ignite-developers.2346864.n4.nabble.
>  com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
>  http://apache-ignite-developers.2346864.n4.nabble.
>  com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
> 
>  —
>  Denis
> 
> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh  >
>  wrote:
> >
> > Denis,
> > Any plans to add 1.8.0 in readme.io for new features?
> > -Roman
> >   On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
>  dma...@apache.org> wrote:
> >
> >
> > Igor,
> >
> > It makes sense to wait for me while everything gets merged into 1.8
>  then. Please let me know over this discussion when the overall merge
>  happens.
> >
> > —
> > Denis
> >
> >> On Nov 15, 2016, at 1:45 AM, Igor Sapego 
> wrote:
> >>
> >> Denis,
> >>
> >> I can merge PDO-related changes into 1.8 but without DML they will
>  break tests
> >> and even compilation so I don't see any sense in doing that before
> DML
>  is merged.
> >>
> >> After DML is ready and merged I'll need some time to merge my
> changes
>  and check
> >> that everything works as intended. The code itself, tests and
> examples
>  are ready.
> >>
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Tue, Nov 15, 2016 at 11:31 AM, Pavel Tupitsyn <
> ptupit...@apache.org
>  > wrote:
> >> Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor binary
>  mode)
> >> is not a simple thing. We won't be able to do that for 1.8.
> >> Other than that, I'll try to fit as many of them as I can. But I
> can't
> >> answer your question since I don't see any date yet.
> >>
> >> By the way, you were going to help with the reviews.
> >>
> >> [1] 

Re: Apache Ignite 1.8 Release

[Denis Magda]

Alexander,

Awesome news, thanks for making this happen!

Igor S., have you merged all ODBC-DML-PHP/PDO related changes? Can I start 
testing that PHP-PDO guidance [1] is correct?

[1] https://apacheignite.readme.io/docs/pdo-interoperability 


—
Denis
 
> On Nov 23, 2016, at 12:01 AM, Alexander Paschenko 
>  wrote:
> 
> Folks,
> 
> Yesterday it'd been agreed with Sergi that DML branch is now good to
> be included into 1.8 branch that is to be created.
> 
> Minor review fixes, should they be made, and test fixes will be
> incorporated into 1.8 as separate patches later.
> 
> Also, it'd been agreed that, in order to deliver these new features on
> time, two subtasks will be fixed in later releases (shortly):
> 
> https://issues.apache.org/jira/browse/IGNITE-4268
> https://issues.apache.org/jira/browse/IGNITE-4269
> 
> On failing tests:
> https://issues.apache.org/jira/browse/IGNITE-2294?focusedCommentId=15683377
> 
> - Alex
> 
> 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> :
>> Vlad,
>> 
>> Most likely today.
>> 
>> - Alex
>> 
>> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
>>> Igniters,
>>> 
>>> I went through remaining tickets assigned to 1.8 and it seems that we are
>>> pretty close to release. As far as I understand the biggest remaining
>>> feature is DML [1]. I think we can create separate branch for 1.8 as soon
>>> as it is merged. Alex, do you have any idea on when it might happen?
>>> 
>>> Vladimir.
>>> 
>>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
>>> 
>>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda  wrote:
>>> 
 Roman,
 
 That versions will be created after 1.8 gets released. Recently there was
 a discussion on the dev list [1] regarding the difficulties related to
 documentation maintenance when several documentation versions co-exist at
 the same time.
 
 It was decided that rather then create a new version for the documentation
 once a new feature added to Ignite it’s better to create a hidden page
 under the current documentation version and make it visible once the next
 version is created after the release.
 
 The bottom line is that, please create a hidden page with a suffix
 “page_name-1.8” and once 1.8 gets released Prachi will create readme.io <
 http://readme.io/> 1.8 and make your doc visible.
 
 [1] http://apache-ignite-developers.2346864.n4.nabble.
 com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
 http://apache-ignite-developers.2346864.n4.nabble.
 com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
 
 —
 Denis
 
> On Nov 16, 2016, at 5:00 PM, Roman Shtykh 
 wrote:
> 
> Denis,
> Any plans to add 1.8.0 in readme.io for new features?
> -Roman
>   On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
 dma...@apache.org> wrote:
> 
> 
> Igor,
> 
> It makes sense to wait for me while everything gets merged into 1.8
 then. Please let me know over this discussion when the overall merge
 happens.
> 
> —
> Denis
> 
>> On Nov 15, 2016, at 1:45 AM, Igor Sapego  wrote:
>> 
>> Denis,
>> 
>> I can merge PDO-related changes into 1.8 but without DML they will
 break tests
>> and even compilation so I don't see any sense in doing that before DML
 is merged.
>> 
>> After DML is ready and merged I'll need some time to merge my changes
 and check
>> that everything works as intended. The code itself, tests and examples
 are ready.
>> 
>> 
>> Best Regards,
>> Igor
>> 
>> On Tue, Nov 15, 2016 at 11:31 AM, Pavel Tupitsyn > wrote:
>> Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor binary
 mode)
>> is not a simple thing. We won't be able to do that for 1.8.
>> Other than that, I'll try to fit as many of them as I can. But I can't
>> answer your question since I don't see any date yet.
>> 
>> By the way, you were going to help with the reviews.
>> 
>> [1] https://issues.apache.org/jira/browse/IGNITE-4128 <
 https://issues.apache.org/jira/browse/IGNITE-4128>
>> [2] https://issues.apache.org/jira/browse/IGNITE-3825 <
 https://issues.apache.org/jira/browse/IGNITE-3825>
>> 
>> On Tue, Nov 15, 2016 at 4:03 AM, Denis Magda > wrote:
>> 
>>> *Alexander P., Igor S.,*
>>> 
>>> When will your merge all DML and ODBC (PDO) related changes into 1.8
>>> branch? I’m looking forward to go through PDO [1] documentation and be
 sure
>>> that everything works as described on my side.
>>> 
>>> *Pavel,*
>>> 

[GitHub] ignite pull request #1272: IGNITE-4288: Fix for 32-bit verions.

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-4288: Fix for 32-bit verions.



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

$ git pull https://github.com/isapego/ignite ignite-4288

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

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


commit d08f4f268b9dd0a20c2e7adc7a6d7a4b50e292eb
Author: Igor Sapego 
Date:   2016-11-23T16:03:17Z

IGNITE-4288: Fix for 32-bit verions.




---
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-4288) ODBC: Fix ODBC and DML interoperability.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-4288:
---

 Summary: ODBC: Fix ODBC and DML interoperability.
 Key: IGNITE-4288
 URL: https://issues.apache.org/jira/browse/IGNITE-4288
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Affects Versions: 1.7
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.8


Need to fix ODBC-DML interoperability issues on ignite-1.8 branch.



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

[GitHub] ignite pull request #1271: IGNITE-4157 Use discovery custom events instead o...

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

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

IGNITE-4157 Use discovery custom events instead of marshaller and system 
cache

First version of feature's implementation.

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

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

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

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


commit 4a094b424d02fc18ecedf9c895c72fe1594f919d
Author: Sergey Chugunov 
Date:   2016-11-09T12:02:41Z

IGNITE-4147 MarshallerContext API change and draft implementation are added

commit 7b1d321bca8a3513603667dd1f05d8760d23d67c
Author: Sergey Chugunov 
Date:   2016-11-23T15:18:30Z

IGNITE-4157 file-based persistence and requesting missing mapping are 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 #1270: IGNITE-4063 BinaryType.fieldNames() should return...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-4063 BinaryType.fieldNames() should return names in consistent order



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

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

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

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


commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 394d562125519193436026af30b93a9588ba08ba
Author: tledkov-gridgain 
Date:   2016-11-23T15:10:18Z

IGNITE-4063:  keep order of fields in the metadata according with schema




---
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-4287) DML: DELETE statement failed: Invalid number of query parameters. Cannot find 2 parameter.

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-4287:
-

 Summary: DML: DELETE statement failed: Invalid number of query 
parameters. Cannot find 2 parameter.
 Key: IGNITE-4287
 URL: https://issues.apache.org/jira/browse/IGNITE-4287
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 1.8


{code:title=test.java|borderStyle=solid}
  IgniteCache orgCache = 
Ignition.ignite().cache(ORG_CACHE);

orgCache.clear();

for (int z=100; z < 10; z++) {
orgCache.query(new SqlFieldsQuery("insert into Organization (_key, 
name) values (?, ?)").setArgs(z, "GridGain RUS " + Integer.toString(z)));
}

for (int z=100; z < 10; z++) {
if (z > 0 && z % 10 == 0)
System.out.println("Delete " + z);

orgCache.query(new SqlFieldsQuery("delete from Organization where 
_key >= ?").setArgs(z));
}
{code}

The code above failed with IgniteException
{noformat}
Exception in thread "main" javax.cache.CacheException: class 
org.apache.ignite.IgniteException: Invalid number of query parameters. Cannot 
find 2 parameter.
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:761)
at 
org.apache.ignite.examples.datagrid.CacheQueryExample.initialize(CacheQueryExample.java:336)
at 
org.apache.ignite.examples.datagrid.CacheQueryExample.main(CacheQueryExample.java:110)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
parameters. Cannot find 2 parameter.
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:818)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:749)
... 7 more
Caused by: class org.apache.ignite.IgniteCheckedException: Invalid number of 
query parameters. Cannot find 2 parameter.
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1789)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:811)
... 8 more
Caused by: class org.apache.ignite.IgniteException: Invalid number of query 
parameters. Cannot find 2 parameter.
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:634)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:650)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.findParams(GridSqlQuerySplitter.java:604)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:403)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:184)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1277)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.executeUpdateStatement(DmlStatementsProcessor.java:226)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:134)
at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:160)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1266)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:813)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:811)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:1766)
... 9 more

{noformat}



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

[GitHub] ignite pull request #1269: IGNITE-3910: Implemented SQLDescribeParam.

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-3910: Implemented SQLDescribeParam.



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

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

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

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


commit 04bf81e2b48d0985b33e95a7d33bed2e65b84aeb
Author: Igor Sapego 
Date:   2016-11-23T14:38:41Z

IGNITE-3910: Implemented SQLDescribeParam.




---
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 1.8 Release

[Alexander Paschenko]

Regarding failing tests mentioned in IGNITE-4280
(IgniteBinaryCacheQueryTestSuite related ones): reason found
(incorrect handling of old configurations where QueryEntities don't
have keyFields field), working on the patch.

- Alex

2016-11-23 16:01 GMT+03:00 Sergey Kozlov :
> Hi
>
> I've started the testing of the key feature introducing for 1.8: DML
>
> On Wed, Nov 23, 2016 at 1:01 PM, Vladimir Ozerov 
> wrote:
>
>> Hi Alex,
>> That is very good news! I created branch *ignite-1.8* and merged your
>> changes there. Thank you for contribution!
>>
>> Igniters,
>> Let's finalize all remaining tickets in the scope of *ignite-1.8 *branch.
>> Hopefully we will be ready for vote in several days.
>>
>> Vladimir.
>>
>> On Wed, Nov 23, 2016 at 11:01 AM, Alexander Paschenko <
>> alexander.a.pasche...@gmail.com> wrote:
>>
>> > Folks,
>> >
>> > Yesterday it'd been agreed with Sergi that DML branch is now good to
>> > be included into 1.8 branch that is to be created.
>> >
>> > Minor review fixes, should they be made, and test fixes will be
>> > incorporated into 1.8 as separate patches later.
>> >
>> > Also, it'd been agreed that, in order to deliver these new features on
>> > time, two subtasks will be fixed in later releases (shortly):
>> >
>> > https://issues.apache.org/jira/browse/IGNITE-4268
>> > https://issues.apache.org/jira/browse/IGNITE-4269
>> >
>> > On failing tests:
>> > https://issues.apache.org/jira/browse/IGNITE-2294?
>> > focusedCommentId=15683377
>> >
>> > - Alex
>> >
>> > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
>> > :
>> > > Vlad,
>> > >
>> > > Most likely today.
>> > >
>> > > - Alex
>> > >
>> > > 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
>> > >> Igniters,
>> > >>
>> > >> I went through remaining tickets assigned to 1.8 and it seems that we
>> > are
>> > >> pretty close to release. As far as I understand the biggest remaining
>> > >> feature is DML [1]. I think we can create separate branch for 1.8 as
>> > soon
>> > >> as it is merged. Alex, do you have any idea on when it might happen?
>> > >>
>> > >> Vladimir.
>> > >>
>> > >> [1] https://issues.apache.org/jira/browse/IGNITE-2294
>> > >>
>> > >> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
>> wrote:
>> > >>
>> > >>> Roman,
>> > >>>
>> > >>> That versions will be created after 1.8 gets released. Recently there
>> > was
>> > >>> a discussion on the dev list [1] regarding the difficulties related
>> to
>> > >>> documentation maintenance when several documentation versions
>> co-exist
>> > at
>> > >>> the same time.
>> > >>>
>> > >>> It was decided that rather then create a new version for the
>> > documentation
>> > >>> once a new feature added to Ignite it’s better to create a hidden
>> page
>> > >>> under the current documentation version and make it visible once the
>> > next
>> > >>> version is created after the release.
>> > >>>
>> > >>> The bottom line is that, please create a hidden page with a suffix
>> > >>> “page_name-1.8” and once 1.8 gets released Prachi will create
>> > readme.io <
>> > >>> http://readme.io/> 1.8 and make your doc visible.
>> > >>>
>> > >>> [1] http://apache-ignite-developers.2346864.n4.nabble.
>> > >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html
>> <
>> > >>> http://apache-ignite-developers.2346864.n4.nabble.
>> > >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
>> > >>>
>> > >>> —
>> > >>> Denis
>> > >>>
>> > >>> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh
>> > > >
>> > >>> wrote:
>> > >>> >
>> > >>> > Denis,
>> > >>> > Any plans to add 1.8.0 in readme.io for new features?
>> > >>> > -Roman
>> > >>> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
>> > >>> dma...@apache.org> wrote:
>> > >>> >
>> > >>> >
>> > >>> > Igor,
>> > >>> >
>> > >>> > It makes sense to wait for me while everything gets merged into 1.8
>> > >>> then. Please let me know over this discussion when the overall merge
>> > >>> happens.
>> > >>> >
>> > >>> > —
>> > >>> > Denis
>> > >>> >
>> > >>> >> On Nov 15, 2016, at 1:45 AM, Igor Sapego 
>> > wrote:
>> > >>> >>
>> > >>> >> Denis,
>> > >>> >>
>> > >>> >> I can merge PDO-related changes into 1.8 but without DML they will
>> > >>> break tests
>> > >>> >> and even compilation so I don't see any sense in doing that before
>> > DML
>> > >>> is merged.
>> > >>> >>
>> > >>> >> After DML is ready and merged I'll need some time to merge my
>> > changes
>> > >>> and check
>> > >>> >> that everything works as intended. The code itself, tests and
>> > examples
>> > >>> are ready.
>> > >>> >>
>> > >>> >>
>> > >>> >> Best Regards,
>> > >>> >> Igor
>> > >>> >>
>> > >>> >> On Tue, Nov 15, 2016 at 11:31 AM, Pavel Tupitsyn <
>> > ptupit...@apache.org
>> > >>> > wrote:
>> > >>> >> Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor
>> binary
>> > >>> 

Re: Hello

[Dmitriy Setrakyan]

Hi Alex,

Welcome to the Ignite community!

Once you are familiar with the contribution process, please see if there is
a specific Jira ticket you would like work on. We will help you get started.

D.

On Wed, Nov 23, 2016 at 2:24 AM, Vladislav Pyatkov 
wrote:

> Please read https://ignite.apache.org/community/contribute.html#contribute
>
> Looking forward for your contributions!
>
> On Wed, Nov 23, 2016 at 1:15 PM, Александр Меньшиков  >
> wrote:
>
> > I want to contribute.
> >
> > 2016-11-23 13:04 GMT+03:00 Vladislav Pyatkov :
> >
> > > Hi Alex,
> > >
> > > This is Apache Ignite development community.
> > > Are you want to contribute to Ignite or you are have any suggestion?
> > >
> > > On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков <
> > > sharple...@gmail.com>
> > > wrote:
> > >
> > > > Hello
> > > >
> > >
> >
>

[GitHub] ignite pull request #1268: IGNITE-3640 IGFS: Local secondary: Investigate wh...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3640  IGFS: Local secondary: Investigate whether we need 
BufferedInputStream for open operation.



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

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

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

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


commit 7d1e4fb00c5488559d894abe7405003f3562fe92
Author: tledkov-gridgain 
Date:   2016-11-23T13:28:37Z

IGNITE-3640: remove buffer at input stream




---
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: Start Contributing

[Dmitriy Setrakyan]

Hi Nikita,

Welcome to the Ignite community!

Once you are familiar with the contribution process, please see if there is
a specific Jira ticket you would like to get started with.

D.

On Wed, Nov 23, 2016 at 1:55 AM, Alexey Kuznetsov 
wrote:

> Hi, Nikita!
>
> Please read https://ignite.apache.org/community/contribute.html#contribute
>
> Looking forward for your contributions!
>
> On Wed, Nov 23, 2016 at 3:59 PM, Никита Амельчев 
> wrote:
>
> > Hello everybody!
> >
> > I want to contribute this project.
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >
>
>
>
> --
> Alexey Kuznetsov
>

Start contributing

[Максим Козлов]

Hello

-- 
Best regards, Maks Kozlov

Re: Apache Ignite 1.8 Release

[Sergey Kozlov]

Hi

I've started the testing of the key feature introducing for 1.8: DML

On Wed, Nov 23, 2016 at 1:01 PM, Vladimir Ozerov 
wrote:

> Hi Alex,
> That is very good news! I created branch *ignite-1.8* and merged your
> changes there. Thank you for contribution!
>
> Igniters,
> Let's finalize all remaining tickets in the scope of *ignite-1.8 *branch.
> Hopefully we will be ready for vote in several days.
>
> Vladimir.
>
> On Wed, Nov 23, 2016 at 11:01 AM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
> > Folks,
> >
> > Yesterday it'd been agreed with Sergi that DML branch is now good to
> > be included into 1.8 branch that is to be created.
> >
> > Minor review fixes, should they be made, and test fixes will be
> > incorporated into 1.8 as separate patches later.
> >
> > Also, it'd been agreed that, in order to deliver these new features on
> > time, two subtasks will be fixed in later releases (shortly):
> >
> > https://issues.apache.org/jira/browse/IGNITE-4268
> > https://issues.apache.org/jira/browse/IGNITE-4269
> >
> > On failing tests:
> > https://issues.apache.org/jira/browse/IGNITE-2294?
> > focusedCommentId=15683377
> >
> > - Alex
> >
> > 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> > :
> > > Vlad,
> > >
> > > Most likely today.
> > >
> > > - Alex
> > >
> > > 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> > >> Igniters,
> > >>
> > >> I went through remaining tickets assigned to 1.8 and it seems that we
> > are
> > >> pretty close to release. As far as I understand the biggest remaining
> > >> feature is DML [1]. I think we can create separate branch for 1.8 as
> > soon
> > >> as it is merged. Alex, do you have any idea on when it might happen?
> > >>
> > >> Vladimir.
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> > >>
> > >> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda 
> wrote:
> > >>
> > >>> Roman,
> > >>>
> > >>> That versions will be created after 1.8 gets released. Recently there
> > was
> > >>> a discussion on the dev list [1] regarding the difficulties related
> to
> > >>> documentation maintenance when several documentation versions
> co-exist
> > at
> > >>> the same time.
> > >>>
> > >>> It was decided that rather then create a new version for the
> > documentation
> > >>> once a new feature added to Ignite it’s better to create a hidden
> page
> > >>> under the current documentation version and make it visible once the
> > next
> > >>> version is created after the release.
> > >>>
> > >>> The bottom line is that, please create a hidden page with a suffix
> > >>> “page_name-1.8” and once 1.8 gets released Prachi will create
> > readme.io <
> > >>> http://readme.io/> 1.8 and make your doc visible.
> > >>>
> > >>> [1] http://apache-ignite-developers.2346864.n4.nabble.
> > >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html
> <
> > >>> http://apache-ignite-developers.2346864.n4.nabble.
> > >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
> > >>>
> > >>> —
> > >>> Denis
> > >>>
> > >>> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh
>  > >
> > >>> wrote:
> > >>> >
> > >>> > Denis,
> > >>> > Any plans to add 1.8.0 in readme.io for new features?
> > >>> > -Roman
> > >>> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
> > >>> dma...@apache.org> wrote:
> > >>> >
> > >>> >
> > >>> > Igor,
> > >>> >
> > >>> > It makes sense to wait for me while everything gets merged into 1.8
> > >>> then. Please let me know over this discussion when the overall merge
> > >>> happens.
> > >>> >
> > >>> > —
> > >>> > Denis
> > >>> >
> > >>> >> On Nov 15, 2016, at 1:45 AM, Igor Sapego 
> > wrote:
> > >>> >>
> > >>> >> Denis,
> > >>> >>
> > >>> >> I can merge PDO-related changes into 1.8 but without DML they will
> > >>> break tests
> > >>> >> and even compilation so I don't see any sense in doing that before
> > DML
> > >>> is merged.
> > >>> >>
> > >>> >> After DML is ready and merged I'll need some time to merge my
> > changes
> > >>> and check
> > >>> >> that everything works as intended. The code itself, tests and
> > examples
> > >>> are ready.
> > >>> >>
> > >>> >>
> > >>> >> Best Regards,
> > >>> >> Igor
> > >>> >>
> > >>> >> On Tue, Nov 15, 2016 at 11:31 AM, Pavel Tupitsyn <
> > ptupit...@apache.org
> > >>> > wrote:
> > >>> >> Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor
> binary
> > >>> mode)
> > >>> >> is not a simple thing. We won't be able to do that for 1.8.
> > >>> >> Other than that, I'll try to fit as many of them as I can. But I
> > can't
> > >>> >> answer your question since I don't see any date yet.
> > >>> >>
> > >>> >> By the way, you were going to help with the reviews.
> > >>> >>
> > >>> >> [1] https://issues.apache.org/jira/browse/IGNITE-4128 <
> > >>> https://issues.apache.org/jira/browse/IGNITE-4128>
> > >>> 

[GitHub] ignite pull request #1264: IGNITE-4281

[devozerov]

Github user devozerov closed the pull request at:

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


---
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 #1266: IGNITE-4271

[devozerov]

Github user devozerov closed the pull request at:

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


---
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-4286) Hadoop: use plain property names.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4286:
---

 Summary: Hadoop: use plain property names.
 Key: IGNITE-4286
 URL: https://issues.apache.org/jira/browse/IGNITE-4286
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Minor
 Fix For: 2.0






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

[jira] [Created] (IGNITE-4284) Failed second client node join with continuous query and peer class loading enabled

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-4284:
---

 Summary: Failed second client node join with continuous query and 
peer class loading enabled
 Key: IGNITE-4284
 URL: https://issues.apache.org/jira/browse/IGNITE-4284
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Dmitry Karachentsev
 Fix For: 2.0


Steps to reproduce:
1) Start server with cache and peer class loading enabled.
2) Start client with peer class loading enabled.
3) Start continuous query with custom event filter factory.
4) Start second client -- Fail with NPE or AsserionError.



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

[GitHub] ignite pull request #1267: IGNITE-4284 - Test

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

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

IGNITE-4284 - Test



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

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

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

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


commit 9c636a3fe06b0836de71efaa090b87bcdc1d104d
Author: dkarachentsev 
Date:   2016-11-23T11:48:51Z

IGNITE-4284 - Test




---
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 #1266: IGNITE-4271

[devozerov]

GitHub user devozerov opened a pull request:

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

IGNITE-4271



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

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

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

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


commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 77f5f4f5c808d839831ebf88ea5581f06a0b0c7f
Author: devozerov 
Date:   2016-11-23T11:40:41Z

Moved to proper packages.

commit d23e228f3cf0075fc955c41c17f6fcac9faeffdf
Author: devozerov 
Date:   2016-11-23T11:42:13Z

Implemented message interface.

commit 3b33e3925e6cb05ac507cdbce65bcd176717f4b8
Author: devozerov 
Date:   2016-11-23T11:48:26Z

Finished.




---
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 #1265: IGNITE-4016: IGNITE-4016: ODBC example now uses D...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-4016: IGNITE-4016: ODBC example now uses DML.



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

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

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

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


commit d3c053ccc071c0afac0f9d8d2a5a1e2d77a5908a
Author: Igor Sapego 
Date:   2016-11-23T11:33:55Z

IGNITE-4016: IGNITE-4016: ODBC example now uses DML.




---
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 #1264: IGNITE-4281

[devozerov]

GitHub user devozerov opened a pull request:

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

IGNITE-4281



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

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

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

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


commit b038730ee56a662f73e02bbec83eb1712180fa82
Author: isapego 
Date:   2016-11-23T09:05:54Z

IGNITE-4249: ODBC: Fixed performance issue caused by ineddicient IO 
handling on CPP side. This closes #1254.

commit 117ef9e25eb4a04690ef9d1261fb615e8cd4eef8
Author: devozerov 
Date:   2016-11-23T11:20:15Z

Reducers context reworked to arrray.

commit c834db290f1356995128024686e626f3ec94e6de
Author: devozerov 
Date:   2016-11-23T11:27:21Z

Finished.

commit 25c24e7788832dbfe226d0cc5cb58d4ce0f1f193
Author: devozerov 
Date:   2016-11-23T11:29:28Z

Minors.




---
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-4282) Javadoc broken

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-4282:


 Summary: Javadoc broken 
 Key: IGNITE-4282
 URL: https://issues.apache.org/jira/browse/IGNITE-4282
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.8
Reporter: Ilya Suntsov
 Fix For: 1.8


Broken javadoc here:
{noformat}incubator-ignite/modules/core/src/main/java/org/apache/ignite/internal/processors/rest/handlers/redis/server/GridRedisDbSizeCommandHandler.java{noformat}

Warning text:
{noformat}Tag @inheritDoc cannot be used in constructor documentation.  It can 
only be used in the following types of documentation: method, inline 
text.{noformat}

Log you can find in attachment.



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

[jira] [Created] (IGNITE-4281) Hadoop: decouple mapper and reducer maps.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4281:
---

 Summary: Hadoop: decouple mapper and reducer maps.
 Key: IGNITE-4281
 URL: https://issues.apache.org/jira/browse/IGNITE-4281
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.7, 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0






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

[jira] [Created] (IGNITE-4280) Fix failing tests in IgniteBinaryCacheQueryTestSuite

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4280:
---

 Summary: Fix failing tests in IgniteBinaryCacheQueryTestSuite
 Key: IGNITE-4280
 URL: https://issues.apache.org/jira/browse/IGNITE-4280
 Project: Ignite
  Issue Type: Test
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
 Fix For: 1.8


Details: 
https://issues.apache.org/jira/browse/IGNITE-2294?focusedCommentId=15683377



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

[jira] [Created] (IGNITE-4279) Make DML related JDBC driver tests pass within suite

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4279:
---

 Summary: Make DML related JDBC driver tests pass within suite
 Key: IGNITE-4279
 URL: https://issues.apache.org/jira/browse/IGNITE-4279
 Project: Ignite
  Issue Type: Test
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
 Fix For: 1.8






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

Re: Hello

[Vladislav Pyatkov]

Please read https://ignite.apache.org/community/contribute.html#contribute

Looking forward for your contributions!

On Wed, Nov 23, 2016 at 1:15 PM, Александр Меньшиков 
wrote:

> I want to contribute.
>
> 2016-11-23 13:04 GMT+03:00 Vladislav Pyatkov :
>
> > Hi Alex,
> >
> > This is Apache Ignite development community.
> > Are you want to contribute to Ignite or you are have any suggestion?
> >
> > On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков <
> > sharple...@gmail.com>
> > wrote:
> >
> > > Hello
> > >
> >
>

Re: Hello

[Александр Меньшиков]

I want to contribute.

2016-11-23 13:04 GMT+03:00 Vladislav Pyatkov :

> Hi Alex,
>
> This is Apache Ignite development community.
> Are you want to contribute to Ignite or you are have any suggestion?
>
> On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков <
> sharple...@gmail.com>
> wrote:
>
> > Hello
> >
>

Re: Hello

[Vladislav Pyatkov]

Hi Alex,

This is Apache Ignite development community.
Are you want to contribute to Ignite or you are have any suggestion?

On Wed, Nov 23, 2016 at 12:41 PM, Александр Меньшиков 
wrote:

> Hello
>

Re: Apache Ignite 1.8 Release

[Vladimir Ozerov]

Hi Alex,
That is very good news! I created branch *ignite-1.8* and merged your
changes there. Thank you for contribution!

Igniters,
Let's finalize all remaining tickets in the scope of *ignite-1.8 *branch.
Hopefully we will be ready for vote in several days.

Vladimir.

On Wed, Nov 23, 2016 at 11:01 AM, Alexander Paschenko <
alexander.a.pasche...@gmail.com> wrote:

> Folks,
>
> Yesterday it'd been agreed with Sergi that DML branch is now good to
> be included into 1.8 branch that is to be created.
>
> Minor review fixes, should they be made, and test fixes will be
> incorporated into 1.8 as separate patches later.
>
> Also, it'd been agreed that, in order to deliver these new features on
> time, two subtasks will be fixed in later releases (shortly):
>
> https://issues.apache.org/jira/browse/IGNITE-4268
> https://issues.apache.org/jira/browse/IGNITE-4269
>
> On failing tests:
> https://issues.apache.org/jira/browse/IGNITE-2294?
> focusedCommentId=15683377
>
> - Alex
>
> 2016-11-22 11:29 GMT+03:00 Alexander Paschenko
> :
> > Vlad,
> >
> > Most likely today.
> >
> > - Alex
> >
> > 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
> >> Igniters,
> >>
> >> I went through remaining tickets assigned to 1.8 and it seems that we
> are
> >> pretty close to release. As far as I understand the biggest remaining
> >> feature is DML [1]. I think we can create separate branch for 1.8 as
> soon
> >> as it is merged. Alex, do you have any idea on when it might happen?
> >>
> >> Vladimir.
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-2294
> >>
> >> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda  wrote:
> >>
> >>> Roman,
> >>>
> >>> That versions will be created after 1.8 gets released. Recently there
> was
> >>> a discussion on the dev list [1] regarding the difficulties related to
> >>> documentation maintenance when several documentation versions co-exist
> at
> >>> the same time.
> >>>
> >>> It was decided that rather then create a new version for the
> documentation
> >>> once a new feature added to Ignite it’s better to create a hidden page
> >>> under the current documentation version and make it visible once the
> next
> >>> version is created after the release.
> >>>
> >>> The bottom line is that, please create a hidden page with a suffix
> >>> “page_name-1.8” and once 1.8 gets released Prachi will create
> readme.io <
> >>> http://readme.io/> 1.8 and make your doc visible.
> >>>
> >>> [1] http://apache-ignite-developers.2346864.n4.nabble.
> >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
> >>> http://apache-ignite-developers.2346864.n4.nabble.
> >>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
> >>>
> >>> —
> >>> Denis
> >>>
> >>> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh  >
> >>> wrote:
> >>> >
> >>> > Denis,
> >>> > Any plans to add 1.8.0 in readme.io for new features?
> >>> > -Roman
> >>> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
> >>> dma...@apache.org> wrote:
> >>> >
> >>> >
> >>> > Igor,
> >>> >
> >>> > It makes sense to wait for me while everything gets merged into 1.8
> >>> then. Please let me know over this discussion when the overall merge
> >>> happens.
> >>> >
> >>> > —
> >>> > Denis
> >>> >
> >>> >> On Nov 15, 2016, at 1:45 AM, Igor Sapego 
> wrote:
> >>> >>
> >>> >> Denis,
> >>> >>
> >>> >> I can merge PDO-related changes into 1.8 but without DML they will
> >>> break tests
> >>> >> and even compilation so I don't see any sense in doing that before
> DML
> >>> is merged.
> >>> >>
> >>> >> After DML is ready and merged I'll need some time to merge my
> changes
> >>> and check
> >>> >> that everything works as intended. The code itself, tests and
> examples
> >>> are ready.
> >>> >>
> >>> >>
> >>> >> Best Regards,
> >>> >> Igor
> >>> >>
> >>> >> On Tue, Nov 15, 2016 at 11:31 AM, Pavel Tupitsyn <
> ptupit...@apache.org
> >>> > wrote:
> >>> >> Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor binary
> >>> mode)
> >>> >> is not a simple thing. We won't be able to do that for 1.8.
> >>> >> Other than that, I'll try to fit as many of them as I can. But I
> can't
> >>> >> answer your question since I don't see any date yet.
> >>> >>
> >>> >> By the way, you were going to help with the reviews.
> >>> >>
> >>> >> [1] https://issues.apache.org/jira/browse/IGNITE-4128 <
> >>> https://issues.apache.org/jira/browse/IGNITE-4128>
> >>> >> [2] https://issues.apache.org/jira/browse/IGNITE-3825 <
> >>> https://issues.apache.org/jira/browse/IGNITE-3825>
> >>> >>
> >>> >> On Tue, Nov 15, 2016 at 4:03 AM, Denis Magda  >>> > wrote:
> >>> >>
> >>> >>> *Alexander P., Igor S.,*
> >>> >>>
> >>> >>> When will your merge all DML and ODBC (PDO) related changes into
> 1.8
> >>> >>> branch? I’m looking forward to go through PDO [1] documentation
> 

Re: Start Contributing

[Alexey Kuznetsov]

Hi, Nikita!

Please read https://ignite.apache.org/community/contribute.html#contribute

Looking forward for your contributions!

On Wed, Nov 23, 2016 at 3:59 PM, Никита Амельчев 
wrote:

> Hello everybody!
>
> I want to contribute this project.
>
> --
> Best wishes,
> Amelchev Nikita
>



-- 
Alexey Kuznetsov

[jira] [Created] (IGNITE-4278) Hadoop: investigate why small array copying is slow on PPC.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4278:
---

 Summary: Hadoop: investigate why small array copying is slow on 
PPC.
 Key: IGNITE-4278
 URL: https://issues.apache.org/jira/browse/IGNITE-4278
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0






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

[jira] [Created] (IGNITE-4277) Hadoop: support raw comparator.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4277:
---

 Summary: Hadoop: support raw comparator.
 Key: IGNITE-4277
 URL: https://issues.apache.org/jira/browse/IGNITE-4277
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0






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

[jira] [Created] (IGNITE-4276) Hadoop: control shuffle jobs "sleep" backpressure with property.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4276:
---

 Summary: Hadoop: control shuffle jobs "sleep" backpressure with 
property.
 Key: IGNITE-4276
 URL: https://issues.apache.org/jira/browse/IGNITE-4276
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


Currently we simply sleep between shuffle job iterations for 5 milliseconds 
(hard-coded). Let's get more control around it.



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

[jira] [Created] (IGNITE-4274) Hadoop: control shuffle message buffer size through property.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4274:
---

 Summary: Hadoop: control shuffle message buffer size through 
property.
 Key: IGNITE-4274
 URL: https://issues.apache.org/jira/browse/IGNITE-4274
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


Currently it is hard-coded to 128Kb.



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

[jira] [Created] (IGNITE-4275) Hadoop: create separate property to avoid sorting of mapper output.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4275:
---

 Summary: Hadoop: create separate property to avoid sorting of 
mapper output.
 Key: IGNITE-4275
 URL: https://issues.apache.org/jira/browse/IGNITE-4275
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


Currently it is "merged" with reducer sorting flag.



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

[jira] [Created] (IGNITE-4273) Hadoop: implement head-based data structures.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4273:
---

 Summary: Hadoop: implement head-based data structures.
 Key: IGNITE-4273
 URL: https://issues.apache.org/jira/browse/IGNITE-4273
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


We store output offheap what causes a lot of offheap <-> heap transitions. Also 
it doesn't allow is to use raw comparator. 

Let's add new data structures which utilize heap arrays.



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

[jira] [Created] (IGNITE-4272) Hadoop: shuffle messages must always be processed asynchronously wtr to shuffle job or mapper.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4272:
---

 Summary: Hadoop: shuffle messages must always be processed 
asynchronously wtr to shuffle job or mapper.
 Key: IGNITE-4272
 URL: https://issues.apache.org/jira/browse/IGNITE-4272
 Project: Ignite
  Issue Type: Sub-task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


Currently we run "GridIoManager.send()" from shuffle job. If it hit local node, 
then message will be processed synchronously, stalling shuffling process for 
other mappers.

Need to ensure that it is always routed to internal pool instead.



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

[jira] [Created] (IGNITE-4271) Hadoop messages must use "direct marshallable" infrastructure.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4271:
---

 Summary: Hadoop messages must use "direct marshallable" 
infrastructure.
 Key: IGNITE-4271
 URL: https://issues.apache.org/jira/browse/IGNITE-4271
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: 1.7, 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0






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

Start Contributing

[Никита Амельчев]

Hello everybody!

I want to contribute this project.

-- 
Best wishes,
Amelchev Nikita

[jira] [Created] (IGNITE-4270) Hadoop: optionally stripe mapper output for every partition.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4270:
---

 Summary: Hadoop: optionally stripe mapper output for every 
partition.
 Key: IGNITE-4270
 URL: https://issues.apache.org/jira/browse/IGNITE-4270
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: 1.8
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.0


Currently we have R maps for M mappers, where R is number of reducers. For this 
reason many mappers writes to concurrent offheap data structure, loosing time 
on concurrency burden.

Let's add an option to create R * M maps, so that every mapper has dedicated 
map for every reducer. This will eliminate almost all concurrency overhead.



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

Re: Apache Ignite 1.8 Release

[Alexander Paschenko]

Folks,

Yesterday it'd been agreed with Sergi that DML branch is now good to
be included into 1.8 branch that is to be created.

Minor review fixes, should they be made, and test fixes will be
incorporated into 1.8 as separate patches later.

Also, it'd been agreed that, in order to deliver these new features on
time, two subtasks will be fixed in later releases (shortly):

https://issues.apache.org/jira/browse/IGNITE-4268
https://issues.apache.org/jira/browse/IGNITE-4269

On failing tests:
https://issues.apache.org/jira/browse/IGNITE-2294?focusedCommentId=15683377

- Alex

2016-11-22 11:29 GMT+03:00 Alexander Paschenko
:
> Vlad,
>
> Most likely today.
>
> - Alex
>
> 2016-11-22 11:25 GMT+03:00 Vladimir Ozerov :
>> Igniters,
>>
>> I went through remaining tickets assigned to 1.8 and it seems that we are
>> pretty close to release. As far as I understand the biggest remaining
>> feature is DML [1]. I think we can create separate branch for 1.8 as soon
>> as it is merged. Alex, do you have any idea on when it might happen?
>>
>> Vladimir.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-2294
>>
>> On Thu, Nov 17, 2016 at 4:06 AM, Denis Magda  wrote:
>>
>>> Roman,
>>>
>>> That versions will be created after 1.8 gets released. Recently there was
>>> a discussion on the dev list [1] regarding the difficulties related to
>>> documentation maintenance when several documentation versions co-exist at
>>> the same time.
>>>
>>> It was decided that rather then create a new version for the documentation
>>> once a new feature added to Ignite it’s better to create a hidden page
>>> under the current documentation version and make it visible once the next
>>> version is created after the release.
>>>
>>> The bottom line is that, please create a hidden page with a suffix
>>> “page_name-1.8” and once 1.8 gets released Prachi will create readme.io <
>>> http://readme.io/> 1.8 and make your doc visible.
>>>
>>> [1] http://apache-ignite-developers.2346864.n4.nabble.
>>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html <
>>> http://apache-ignite-developers.2346864.n4.nabble.
>>> com/Maintaining-documentation-consistency-on-readme-io-td10868.html>
>>>
>>> —
>>> Denis
>>>
>>> > On Nov 16, 2016, at 5:00 PM, Roman Shtykh 
>>> wrote:
>>> >
>>> > Denis,
>>> > Any plans to add 1.8.0 in readme.io for new features?
>>> > -Roman
>>> >On Wednesday, November 16, 2016 6:08 AM, Denis Magda <
>>> dma...@apache.org> wrote:
>>> >
>>> >
>>> > Igor,
>>> >
>>> > It makes sense to wait for me while everything gets merged into 1.8
>>> then. Please let me know over this discussion when the overall merge
>>> happens.
>>> >
>>> > —
>>> > Denis
>>> >
>>> >> On Nov 15, 2016, at 1:45 AM, Igor Sapego  wrote:
>>> >>
>>> >> Denis,
>>> >>
>>> >> I can merge PDO-related changes into 1.8 but without DML they will
>>> break tests
>>> >> and even compilation so I don't see any sense in doing that before DML
>>> is merged.
>>> >>
>>> >> After DML is ready and merged I'll need some time to merge my changes
>>> and check
>>> >> that everything works as intended. The code itself, tests and examples
>>> are ready.
>>> >>
>>> >>
>>> >> Best Regards,
>>> >> Igor
>>> >>
>>> >> On Tue, Nov 15, 2016 at 11:31 AM, Pavel Tupitsyn >> > wrote:
>>> >> Denis, [1] depends on [2], and [2](.NET: CacheEntryProcessor binary
>>> mode)
>>> >> is not a simple thing. We won't be able to do that for 1.8.
>>> >> Other than that, I'll try to fit as many of them as I can. But I can't
>>> >> answer your question since I don't see any date yet.
>>> >>
>>> >> By the way, you were going to help with the reviews.
>>> >>
>>> >> [1] https://issues.apache.org/jira/browse/IGNITE-4128 <
>>> https://issues.apache.org/jira/browse/IGNITE-4128>
>>> >> [2] https://issues.apache.org/jira/browse/IGNITE-3825 <
>>> https://issues.apache.org/jira/browse/IGNITE-3825>
>>> >>
>>> >> On Tue, Nov 15, 2016 at 4:03 AM, Denis Magda >> > wrote:
>>> >>
>>> >>> *Alexander P., Igor S.,*
>>> >>>
>>> >>> When will your merge all DML and ODBC (PDO) related changes into 1.8
>>> >>> branch? I’m looking forward to go through PDO [1] documentation and be
>>> sure
>>> >>> that everything works as described on my side.
>>> >>>
>>> >>> *Pavel,*
>>> >>>
>>> >>> Do you think it will be possible to complete all the .NET usability
>>> >>> tickets [2] under 1.8 and roll them out to the Apache Ignite users?
>>> >>>
>>> >>> [1] https://issues.apache.org/jira/browse/IGNITE-3921 <
>>> https://issues.apache.org/jira/browse/IGNITE-3921>
>>> >>> [2] https://issues.apache.org/jira/browse/IGNITE-4114 <
>>> https://issues.apache.org/jira/browse/IGNITE-4114>
>>> >>>
>>> >>> —
>>> >>> Denis
>>> >>>
>>> >>> On Nov 9, 2016, at 6:55 AM, Denis Magda > dma...@gridgain.com>> wrote:
>>>