[GitHub] ignite pull request: Ignite 2218b

[asfgit]

Github user asfgit closed the pull request at:

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


---
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.
---

[RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

[Anton Vinogradov]

Hello!

Apache Ignite 1.5.0.final release (RC3) has been accepted.

13 "+1" votes received.

Here are the votes received:

   - Anton Vinogradov (binding)
   - Nikolay Tikhonov (binding)
   - Konstantin Boudnik (binding)
   - Semyon Boikov (binding)
   - Gianfranco Murador (binding)
   - Vladimir Ozerov (binding)
   - Alexey Goncharuk (binding)
   - Raul Kripalani (binding)
   - Denis Magda (binding)
   - Sergi Vladykin (binding)
   - 姜 为
   - Alexey Kuznetsov
   - Roman Shtykh

Here is the link to vote thread -
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-5-0-final-RC3-td6305.html

Ignite 1.5.0.final successfuly released to
https://dist.apache.org/repos/dist/release/ignite/1.5.0.final/

Site & Maven will be updated soon.

Thanks!

Need help with JIRA ticket

[chandresh pancholi]

Hi Igniters,

I have started working on this ticket
https://issues.apache.org/jira/browse/IGNITE-949. If anyone of you can help
me out on how to start implementing JIRA tickets.

Thanks in advance

-- 
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:chandresh.panch...@flipkart.com
Contact:08951803660

Re: SQL query doesn't work with binary marshaller

[Vladimir Ozerov]

Yes, here it is - https://issues.apache.org/jira/browse/IGNITE-2208

On Thu, Dec 31, 2015 at 1:05 AM, Dmitriy Setrakyan 
wrote:

> Vladimir, do you know the ticket number?
>
> On Wed, Dec 30, 2015 at 9:23 AM, Vladimir Ozerov 
> wrote:
>
> > This is a known problem, scheduled for 1.6. You can find corresponding
> > ticket on TC runs - it is mentioned in one of muted Binary Queries tests.
> > 30 дек. 2015 г. 20:04 пользователь "Andrey Gura" 
> > написал:
> >
> > > Guys,
> > >
> > > I found problem with SqlQuery and binary objects. TC is green but log
> for
> > > Ignite Binary Objects Queries plan on ignite-1.5 branch contains errors
> > in
> > > IgniteCacheAbstractQuerySelfTest.testObjectQuery.
> > >
> > > The following code leads to empty result because rows have
> > BinaryObjectImpl
> > > type while query arg has ValueObject type (comparison fails):
> > >
> > >
> > > IgniteCache cache = ignite().cache(null);
> > >
> > > ObjectValue val = new ObjectValue("test", 0);
> > >
> > > cache.put(1, val);
> > >
> > > QueryCursor> qry =
> > > cache.query(new SqlQuery > > ObjectValue>(ObjectValue.class, "_val=?").setArgs(val));
> > >
> > > Iterator> iter =
> > qry.iterator();
> > > // empty iterator
> > >
> > >
> > >
> > > Is it known issue or I should create a ticket?
> > >
> > > --
> > > Andrey Gura
> > > GridGain Systems, Inc.
> > > www.gridgain.com
> > >
> >
>

[jira] [Created] (IGNITE-2332) Service proxy can't be created for package-private implementation

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2332:
---

 Summary: Service proxy can't be created for package-private 
implementation
 Key: IGNITE-2332
 URL: https://issues.apache.org/jira/browse/IGNITE-2332
 Project: Ignite
  Issue Type: Bug
  Components: managed services
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
 Fix For: 1.6


{noformat}
Caused by: java.lang.IllegalAccessException: Class 
org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable
 can not access a member of class 
org.apache.ignite.examples.service.MyServiceImpl with modifiers "public"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:109)
at 
java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:261)
at 
java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:253)
at java.lang.reflect.Method.invoke(Method.java:599)
at 
org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:382)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1789)
at 
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6372)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
at 
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1166)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1770)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:823)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:105)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:786)
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)
{noformat}



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

Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

[Konstantin Boudnik]

Running into some issues with Zeppelin integration and have noticed that the
version reported by the node in the log isn't the same as the version just
released. It says
1.5.0-final
instead of
1.5.0.final

Cos

On Mon, Jan 04, 2016 at 01:12PM, Anton Vinogradov wrote:
> Hello!
> 
> Apache Ignite 1.5.0.final release (RC3) has been accepted.
> 
> 13 "+1" votes received.
> 
> Here are the votes received:
> 
>- Anton Vinogradov (binding)
>- Nikolay Tikhonov (binding)
>- Konstantin Boudnik (binding)
>- Semyon Boikov (binding)
>- Gianfranco Murador (binding)
>- Vladimir Ozerov (binding)
>- Alexey Goncharuk (binding)
>- Raul Kripalani (binding)
>- Denis Magda (binding)
>- Sergi Vladykin (binding)
>- 姜 为
>- Alexey Kuznetsov
>- Roman Shtykh
> 
> Here is the link to vote thread -
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-5-0-final-RC3-td6305.html
> 
> Ignite 1.5.0.final successfuly released to
> https://dist.apache.org/repos/dist/release/ignite/1.5.0.final/
> 
> Site & Maven will be updated soon.
> 
> Thanks!


signature.asc
Description: Digital signature

[jira] [Created] (IGNITE-2331) RxJava Intergration

[Lukas Eichler (JIRA)]

Lukas Eichler created IGNITE-2331:
-

 Summary: RxJava Intergration
 Key: IGNITE-2331
 URL: https://issues.apache.org/jira/browse/IGNITE-2331
 Project: Ignite
  Issue Type: Wish
Reporter: Lukas Eichler


Add direct support by RxJava by providing: 
1. "getObervable"-method for async operations that is similar to the 
"future"-method but creates Obervables instead of IgniteFutures
2. "toObervable"-method on igniteFutures that creates an Observable from the 
IgniteFuture



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

[GitHub] ignite pull request: IGNITE-429: Apache Storm Streamer

[shroman]

GitHub user shroman opened a pull request:

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

IGNITE-429: Apache Storm Streamer



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

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

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

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


commit 8420e109c4d07bbf438f17dc79268c39b47e76b2
Author: chandresh pancholi 
Date:   2015-09-15T12:50:30Z

ignite-429 feature fix

commit a5adeb4c7badd52dd7724fa5a9a9ba7924e934ed
Author: chandresh pancholi 
Date:   2015-09-16T13:19:37Z

Ignite code refactor and modification

commit c6335046a07d9859a46d078e6cd8d7d2a7011df2
Author: chandresh pancholi 
Date:   2015-09-21T11:59:24Z

Code refactor

commit 4596bedfbfc756d3974b4d2270401515fa618bb5
Author: chandresh pancholi 
Date:   2015-09-28T09:12:13Z

Work completed

commit 538986b186b3d89797a34fe35c8120fecaf9
Author: chandresh pancholi 
Date:   2015-09-29T11:37:17Z

Apache ignite-storm integration

commit 3f40de788e5a050bbefb69ac2517a625e72b5299
Author: chandresh pancholi 
Date:   2015-09-29T11:37:50Z

exclusion of zookeeper

commit aa59cdade93d41d877b1966c4851aa827981b73c
Author: chandresh pancholi 
Date:   2015-10-03T12:13:18Z

Implemented Refactor suggestion given by Anton in Ignite0429

commit 2e103b915ba88b38604030092f55ed1f04b14cfe
Author: chandresh pancholi 
Date:   2015-10-05T07:43:02Z

Code refactor in storm module suggested by Gian/Anton

commit 7fa633cfb0cfb8144e780d9572a3a4fbe518bbd4
Author: chandresh pancholi 
Date:   2015-10-07T08:52:12Z

Adding javadoc in StormSpout class and make streamer compatible with java1.7

commit c181e3d7bf55f91cc0ccfa0407fae72f4c1274c3
Author: chandresh pancholi 
Date:   2015-10-07T13:18:44Z

added assertEqual in Storm tests

commit 96b1095f3b6bfbaedb02974c66acbca2cfc8c9bf
Author: chandresh pancholi 
Date:   2015-10-07T13:19:52Z

added assertEqual in Storm tests

commit d11a0d89aab610998cfc32fca8ddb9b2e01d7854
Author: chandresh pancholi 
Date:   2015-10-09T08:07:10Z

Remove no. of  workers from test class and changed the time out

commit 67baeb940006e5054dd7b6c4994a2907071ecb68
Author: chandresh pancholi 
Date:   2015-10-19T11:53:24Z

Generation of another node in ignite unit test

commit 39ef112dacbd410d6955641fa59d74b9c691e91f
Author: Anton Vinogradov 
Date:   2015-11-23T10:58:05Z

Merge remote-tracking branch 'remotes/origin/ignite-1.5' into 
ignite-429-pull-fixes

Conflicts:
pom.xml

commit 39f5e40952c5e636b1116a200921df2258a6e27a
Author: Anton Vinogradov 
Date:   2015-11-23T10:58:45Z

Merge remote-tracking branch 'remotes/origin/ignite-1.5' into 
ignite-429-pull-fixes

Conflicts:
pom.xml

commit d67994e381e83cd6bda627925e561c15ad2fe5c3
Author: Anton Vinogradov 
Date:   2015-11-23T10:59:17Z

429 Pull request fixes

commit 4127c22a99136bd04850ee35c7181d4c49193393
Author: shtykh_roman 
Date:   2016-01-05T05:54:49Z

IGNITE-429: IgniteStormStreamer implementation reworked.

commit bae4d447ad694bcd1daa9795ba8223d4d57029ca
Author: shtykh_roman 
Date:   2016-01-05T06:42:50Z

IGNITE-429: IgniteStormStreamer implementation reworked. Changes test 
configuration.




---
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: Version mismatch Was: [RESULT] [VOTE] Apache Ignite 1.5.0.final Release (RC3)

[Dmitriy Setrakyan]

Cos, this seems to be just a typo. The actual release version in maven is
1.5.0.final.

On Mon, Jan 4, 2016 at 8:04 PM, Konstantin Boudnik  wrote:

> Running into some issues with Zeppelin integration and have noticed that
> the
> version reported by the node in the log isn't the same as the version just
> released. It says
> 1.5.0-final
> instead of
> 1.5.0.final
>
> Cos
>
> On Mon, Jan 04, 2016 at 01:12PM, Anton Vinogradov wrote:
> > Hello!
> >
> > Apache Ignite 1.5.0.final release (RC3) has been accepted.
> >
> > 13 "+1" votes received.
> >
> > Here are the votes received:
> >
> >- Anton Vinogradov (binding)
> >- Nikolay Tikhonov (binding)
> >- Konstantin Boudnik (binding)
> >- Semyon Boikov (binding)
> >- Gianfranco Murador (binding)
> >- Vladimir Ozerov (binding)
> >- Alexey Goncharuk (binding)
> >- Raul Kripalani (binding)
> >- Denis Magda (binding)
> >- Sergi Vladykin (binding)
> >- 姜 为
> >- Alexey Kuznetsov
> >- Roman Shtykh
> >
> > Here is the link to vote thread -
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-1-5-0-final-RC3-td6305.html
> >
> > Ignite 1.5.0.final successfuly released to
> > https://dist.apache.org/repos/dist/release/ignite/1.5.0.final/
> >
> > Site & Maven will be updated soon.
> >
> > Thanks!
>

Re: SQL query doesn't work with binary marshaller

[Konstantin Boudnik]

I have reported what might be a similar issue on the separate thread with subj
"Differences in default marshaller"

Cos

On Mon, Jan 04, 2016 at 01:39PM, Vladimir Ozerov wrote:
> Yes, here it is - https://issues.apache.org/jira/browse/IGNITE-2208
> 
> On Thu, Dec 31, 2015 at 1:05 AM, Dmitriy Setrakyan 
> wrote:
> 
> > Vladimir, do you know the ticket number?
> >
> > On Wed, Dec 30, 2015 at 9:23 AM, Vladimir Ozerov 
> > wrote:
> >
> > > This is a known problem, scheduled for 1.6. You can find corresponding
> > > ticket on TC runs - it is mentioned in one of muted Binary Queries tests.
> > > 30 дек. 2015 г. 20:04 пользователь "Andrey Gura" 
> > > написал:
> > >
> > > > Guys,
> > > >
> > > > I found problem with SqlQuery and binary objects. TC is green but log
> > for
> > > > Ignite Binary Objects Queries plan on ignite-1.5 branch contains errors
> > > in
> > > > IgniteCacheAbstractQuerySelfTest.testObjectQuery.
> > > >
> > > > The following code leads to empty result because rows have
> > > BinaryObjectImpl
> > > > type while query arg has ValueObject type (comparison fails):
> > > >
> > > >
> > > > IgniteCache cache = ignite().cache(null);
> > > >
> > > > ObjectValue val = new ObjectValue("test", 0);
> > > >
> > > > cache.put(1, val);
> > > >
> > > > QueryCursor> qry =
> > > > cache.query(new SqlQuery > > > ObjectValue>(ObjectValue.class, "_val=?").setArgs(val));
> > > >
> > > > Iterator> iter =
> > > qry.iterator();
> > > > // empty iterator
> > > >
> > > >
> > > >
> > > > Is it known issue or I should create a ticket?
> > > >
> > > > --
> > > > Andrey Gura
> > > > GridGain Systems, Inc.
> > > > www.gridgain.com
> > > >
> > >
> >


signature.asc
Description: Digital signature

Re: Need help with JIRA ticket

[chandresh pancholi]

Sure Dmitriy.

Will wait for sometime :) :)

On Mon, Jan 4, 2016 at 11:38 PM, Dmitriy Setrakyan 
wrote:

> Hi Chandresh,
>
> Glad to hear that you are starting to work on Python client for Ignite
> RDDs.
>
> Just want to give you heads up that a good chunk of the community is likely
> to be on a post new year hiatus this week, so don’t despair if you don’t
> get a response right away :)
>
> D.
>
> On Mon, Jan 4, 2016 at 1:32 AM, chandresh pancholi <
> chandreshpancholi...@gmail.com> wrote:
>
> > Hi Igniters,
> >
> > I have started working on this ticket
> > https://issues.apache.org/jira/browse/IGNITE-949. If anyone of you can
> > help
> > me out on how to start implementing JIRA tickets.
> >
> > Thanks in advance
> >
> > --
> > Chandresh Pancholi
> > Senior Software Engineer
> > Flipkart.com
> > Email-id:chandresh.panch...@flipkart.com
> > Contact:08951803660
> >
>



-- 
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:chandresh.panch...@flipkart.com
Contact:08951803660

Re: Differences in default marshaller

[Dmitriy Setrakyan]

Cos, I think the proper fix would be to use the default binary marshaller
on both ends, no?

On Mon, Jan 4, 2016 at 11:05 PM, Konstantin Boudnik  wrote:

> In the interest of full disclosure, I have fixed the failing test as shown
> in
> http://is.gd/HsrHGf but I am fairly sure it might/will pop-up in the
> actual
> deployment, because the client node will be started with
> OptimizedMarshaller
> anyway.
>
> Cos
>
> On Mon, Jan 04, 2016 at 08:40PM, Konstantin Boudnik wrote:
> > Fellas,
> >
> > I have noticed a weird thing while working on upgrading Ignite in
> Zeppelin.
> > One of the tests failed because of
> >
> >  Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node's
> >  marshaller differs from remote node's marshaller (to make sure all
> nodes in
> >  topology have identical marshaller, configure marshaller explicitly in
> >  configuration)
> >
> [locMarshaller=org.apache.ignite.marshaller.optimized.OptimizedMarshaller,
> >  rmtMarshaller=org.apache.ignite.internal.binary.BinaryMarshaller,
> >  locNodeAddrs=[
> testing-worker-linux-docker-a1225458-3234-linux-7.prod.travis-ci.org/0:0:0:0:0:0:0:1%1
> ,
> >  /127.0.0.1, /172.17.12.239], locPort=0,
> >  rmtNodeAddr=[
> testing-worker-linux-docker-a1225458-3234-linux-7.prod.travis-ci.org/0:0:0:0:0:0:0:1%1
> ,
> >  /127.0.0.1, /172.17.12.239],
> locNodeId=8fa598a2-9986-4f29-ba8d-8f857048e227,
> >  rmtNodeId=3aa33408-afea-48c7-941c-8ea87429f44d]
> >
> > At the glance, it seems like running nodes in server and client modes
> somehow
> > trigger different defaults for the marshallers, but I wasn't able to
> quickly
> > find anything in the code proving my point.
> >
> > I've ended up forcing OptimizedMarshaller for the server node in the
> Zep's
> >
>  ignite/src/test/java/org/apache/zeppelin/ignite/IgniteSqlInterpreterTest.java
> > and it solved the immediate issue. However, the situation seems worthy
> noting
> > on dev@
> >
> > Cheers,
> >   Cos
> >
>
>
>

Re: Differences in default marshaller

[Konstantin Boudnik]

In the interest of full disclosure, I have fixed the failing test as shown in
http://is.gd/HsrHGf but I am fairly sure it might/will pop-up in the actual
deployment, because the client node will be started with OptimizedMarshaller
anyway.

Cos

On Mon, Jan 04, 2016 at 08:40PM, Konstantin Boudnik wrote:
> Fellas,
> 
> I have noticed a weird thing while working on upgrading Ignite in Zeppelin.
> One of the tests failed because of
> 
>  Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node's
>  marshaller differs from remote node's marshaller (to make sure all nodes in
>  topology have identical marshaller, configure marshaller explicitly in
>  configuration)
>  [locMarshaller=org.apache.ignite.marshaller.optimized.OptimizedMarshaller,
>  rmtMarshaller=org.apache.ignite.internal.binary.BinaryMarshaller,
>  
> locNodeAddrs=[testing-worker-linux-docker-a1225458-3234-linux-7.prod.travis-ci.org/0:0:0:0:0:0:0:1%1,
>  /127.0.0.1, /172.17.12.239], locPort=0,
>  
> rmtNodeAddr=[testing-worker-linux-docker-a1225458-3234-linux-7.prod.travis-ci.org/0:0:0:0:0:0:0:1%1,
>  /127.0.0.1, /172.17.12.239], locNodeId=8fa598a2-9986-4f29-ba8d-8f857048e227,
>  rmtNodeId=3aa33408-afea-48c7-941c-8ea87429f44d]
> 
> At the glance, it seems like running nodes in server and client modes somehow
> trigger different defaults for the marshallers, but I wasn't able to quickly
> find anything in the code proving my point. 
> 
> I've ended up forcing OptimizedMarshaller for the server node in the Zep's 
>   
> ignite/src/test/java/org/apache/zeppelin/ignite/IgniteSqlInterpreterTest.java
> and it solved the immediate issue. However, the situation seems worthy noting
> on dev@
> 
> Cheers,
>   Cos
> 




signature.asc
Description: Digital signature

Ignite docker image

[Dmitriy Setrakyan]

Gents,

I just looked at the Ignite docker image [1] and it has the following
directive in it:

*ENV IGNITE_HOME /opt/ignite/ignite-fabric-1.0.0-incubating*

Looked like it needs some freshening up.

Nick, given that you have been managing this docker account, can you please
update it?

D.