Re: [VOTE] Apache Ignite 2.0.0 RC1

[Sergey Kozlov]

Thanks Alexey.

Now it fixed and I found more issues for the release candidate:

[1] IGNITE-5122 REST example is broken

[2] IGNITE-5121 REST API call with empty cache name causes NPE


On Sat, Apr 29, 2017 at 5:09 PM, Alexey Kuznetsov 
wrote:

> Sergey,
>
> Good cacth. I think this issue is a blocker to release.
> -1 from me (binding).
>
> However I'v already pushed the fix, please check it.
>
>
> On Sat, Apr 29, 2017 at 8:48 PM, Alexey Kuznetsov 
> wrote:
>
> > Nik,
> >
> > Thanks, that you spotted this issue.
> >
> > Could you provide a simple reproducer & create issue in JIRA?
> >
> >
> > On Sat, Apr 29, 2017 at 6:03 AM, npordash  wrote:
> >
> >> Hi Guys,
> >>
> >> Sorry to post this in a voting thread, but I tried to update a project
> to
> >> 2.0 (using the git tag Denis referred to) and I'm seeing what I assume
> is
> >> a
> >> regression. In short, attempts to access a pre-configured cache within
> the
> >> onIgniteStart() method of a PluginProvider now returns null instead of
> >> returning the cache. In 1.9 this was not returning null.
> >>
> >> Is this an intended behavioral change? According to the javadoc it still
> >> states that Ignite has fully started by the time onIgniteStart() is
> >> invoked.
> >>
> >> Thanks!
> >> -Nick
> >>
> >>
> >>
> >> --
> >> View this message in context: http://apache-ignite-developer
> >> s.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-0-0-RC1-tp17335p17338.html
> >> Sent from the Apache Ignite Developers mailing list archive at
> Nabble.com.
> >>
> >
> >
> >
> > --
> > Alexey Kuznetsov
> >
>
>
>
> --
> Alexey Kuznetsov
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-5122) REST example is broken

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-5122:
-

 Summary: REST example is broken
 Key: IGNITE-5122
 URL: https://issues.apache.org/jira/browse/IGNITE-5122
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Sergey Kozlov
 Fix For: 2.0


REST example {{examples/rest/http-rest-example.php}} is broken due to missing a 
cache name for requests.



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

[jira] [Created] (IGNITE-5121) REST API call with empty cache name causes NPE

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-5121:
-

 Summary: REST API call with empty cache name causes NPE
 Key: IGNITE-5121
 URL: https://issues.apache.org/jira/browse/IGNITE-5121
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Sergey Kozlov
 Fix For: 2.0


Request cache entry without cacheName causes NPE on the node:
{noformat}
[19:58:33,960][SEVERE][qtp153051342-48][GridJettyRestProtocol] Failed to 
process HTTP request [action=/ignite, req=(POST 
/ignite?cmd=get=mykey-529=2128506-ad94-4a21-a711-529=)@2130154253
 org.eclipse.jetty.server.Request@7ef7930d]
class org.apache.ignite.IgniteCheckedException: null
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7242)
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:172)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at 
java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:333)
at 
java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:988)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.cache(GridCacheProcessor.java:3439)
at 
org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler.localCache(GridCacheCommandHandler.java:752)
at 
org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler.executeCommand(GridCacheCommandHandler.java:678)
at 
org.apache.ignite.internal.processors.rest.handlers.cache.GridCacheCommandHandler.handleAsync(GridCacheCommandHandler.java:427)
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:266)
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:89)
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:155)
... 4 more
{noformat}



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

[GitHub] ignite pull request #1889: Ignite 5120

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 5120



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

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

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

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


commit 777078d377ba2f94b8f41086ecf0ad6056cdace5
Author: Alexey Kuznetsov 
Date:   2017-04-29T14:01:47Z

IGNITE-5120 Fixed LGPL build.

commit 006a01bccc41095d660618d10845af63da4750a9
Author: oleg-ostanin 
Date:   2017-04-29T16:44:31Z

IGNITE-5120 fixed hibernate-core compilation




---
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: [VOTE] Apache Ignite 2.0.0 RC1

[Alexey Kuznetsov]

Sergey,

Good cacth. I think this issue is a blocker to release.
-1 from me (binding).

However I'v already pushed the fix, please check it.


On Sat, Apr 29, 2017 at 8:48 PM, Alexey Kuznetsov 
wrote:

> Nik,
>
> Thanks, that you spotted this issue.
>
> Could you provide a simple reproducer & create issue in JIRA?
>
>
> On Sat, Apr 29, 2017 at 6:03 AM, npordash  wrote:
>
>> Hi Guys,
>>
>> Sorry to post this in a voting thread, but I tried to update a project to
>> 2.0 (using the git tag Denis referred to) and I'm seeing what I assume is
>> a
>> regression. In short, attempts to access a pre-configured cache within the
>> onIgniteStart() method of a PluginProvider now returns null instead of
>> returning the cache. In 1.9 this was not returning null.
>>
>> Is this an intended behavioral change? According to the javadoc it still
>> states that Ignite has fully started by the time onIgniteStart() is
>> invoked.
>>
>> Thanks!
>> -Nick
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-developer
>> s.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-0-0-RC1-tp17335p17338.html
>> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>>
>
>
>
> --
> Alexey Kuznetsov
>



-- 
Alexey Kuznetsov

Re: [VOTE] Apache Ignite 2.0.0 RC1

[Alexey Kuznetsov]

Nik,

Thanks, that you spotted this issue.

Could you provide a simple reproducer & create issue in JIRA?


On Sat, Apr 29, 2017 at 6:03 AM, npordash  wrote:

> Hi Guys,
>
> Sorry to post this in a voting thread, but I tried to update a project to
> 2.0 (using the git tag Denis referred to) and I'm seeing what I assume is a
> regression. In short, attempts to access a pre-configured cache within the
> onIgniteStart() method of a PluginProvider now returns null instead of
> returning the cache. In 1.9 this was not returning null.
>
> Is this an intended behavioral change? According to the javadoc it still
> states that Ignite has fully started by the time onIgniteStart() is
> invoked.
>
> Thanks!
> -Nick
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-0-0-
> RC1-tp17335p17338.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>



-- 
Alexey Kuznetsov

Re: [VOTE] Apache Ignite 2.0.0 RC1

[Sergey Kozlov]

Hi

It seems I found the blocker issue [1] for 2.0.0-rc1
Could someone take a look and confirm the priority?

[1] IGNITE-5120 Broken compilation for LGPL fabric edition


On Sat, Apr 29, 2017 at 2:03 AM, npordash  wrote:

> Hi Guys,
>
> Sorry to post this in a voting thread, but I tried to update a project to
> 2.0 (using the git tag Denis referred to) and I'm seeing what I assume is a
> regression. In short, attempts to access a pre-configured cache within the
> onIgniteStart() method of a PluginProvider now returns null instead of
> returning the cache. In 1.9 this was not returning null.
>
> Is this an intended behavioral change? According to the javadoc it still
> states that Ignite has fully started by the time onIgniteStart() is
> invoked.
>
> Thanks!
> -Nick
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-0-0-
> RC1-tp17335p17338.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-5120) Broken compilation for LGPL fabric edition

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-5120:
-

 Summary: Broken compilation for LGPL fabric edition
 Key: IGNITE-5120
 URL: https://issues.apache.org/jira/browse/IGNITE-5120
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 2.0
Reporter: Sergey Kozlov
Priority: Blocker
 Fix For: 2.0


The fabric edition can't be complied with lgpl profile:
{noformat}
mvn clean package  -Prelease,lgpl -Dignite.edition=fabric-lgpl -DskipTests
...
Downloaded: 
https://repo.maven.apache.org/maven2/org/hibernate/hibernate-core/4.2.21.Final/hibernate-core-4.2.21.Final.jar
 (4592 KB at 3578.8 KB/sec)
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] ignite-apache-license-gen .. SUCCESS [ 35.812 s]
[INFO] ignite-tools ... SUCCESS [ 51.923 s]
[INFO] ignite-core  SUCCESS [02:30 min]
[INFO] ignite-log4j ... SUCCESS [  3.119 s]
[INFO] ignite-indexing  SUCCESS [ 12.571 s]
[INFO] ignite-urideploy ... SUCCESS [  4.896 s]
[INFO] ignite-spring .. SUCCESS [  4.876 s]
[INFO] ignite-hadoop .. SUCCESS [ 43.381 s]
[INFO] ignite-extdata-p2p . SUCCESS [  4.034 s]
[INFO] ignite-extdata-uri-dep . SUCCESS [  1.825 s]
[INFO] ignite-extdata-uri . SUCCESS [  1.353 s]
[INFO] ignite-rest-http ... SUCCESS [  5.660 s]
[INFO] ignite-clients . SUCCESS [  3.208 s]
[INFO] ignite-spring-data . SUCCESS [  4.394 s]
[INFO] ignite-web . SUCCESS [  3.048 s]
[INFO] ignite-aop . SUCCESS [  4.712 s]
[INFO] ignite-ssh . SUCCESS [  2.761 s]
[INFO] ignite-jta . SUCCESS [ 13.427 s]
[INFO] ignite-aws . SUCCESS [  8.144 s]
[INFO] ignite-log4j2 .. SUCCESS [  4.777 s]
[INFO] ignite-slf4j ... SUCCESS [  2.809 s]
[INFO] ignite-jcl . SUCCESS [  2.857 s]
[INFO] ignite-codegen . SUCCESS [  2.166 s]
[INFO] ignite-gce . SUCCESS [  7.182 s]
[INFO] ignite-cloud ... SUCCESS [ 33.800 s]
[INFO] ignite-mesos ... SUCCESS [  6.682 s]
[INFO] ignite-kafka ... SUCCESS [ 22.972 s]
[INFO] ignite-flume ... SUCCESS [  7.512 s]
[INFO] ignite-yarn  SUCCESS [ 16.315 s]
[INFO] ignite-jms11 ... SUCCESS [  5.567 s]
[INFO] ignite-twitter . SUCCESS [  7.928 s]
[INFO] ignite-mqtt  SUCCESS [01:05 min]
[INFO] ignite-zookeeper ... SUCCESS [  4.415 s]
[INFO] ignite-camel ... SUCCESS [  7.775 s]
[INFO] ignite-storm ... SUCCESS [ 11.099 s]
[INFO] ignite-osgi-paxlogging . SUCCESS [  0.284 s]
[INFO] ignite-osgi-karaf .. SUCCESS [  0.677 s]
[INFO] ignite-osgi  SUCCESS [ 25.125 s]
[INFO] ignite-appserver-test .. SUCCESS [  0.199 s]
[INFO] ignite-websphere-test .. SUCCESS [  5.006 s]
[INFO] ignite-cassandra ... SUCCESS [  0.088 s]
[INFO] ignite-cassandra-store . SUCCESS [ 36.538 s]
[INFO] ignite-cassandra-serializers ... SUCCESS [  3.664 s]
[INFO] ignite-flink ... SUCCESS [ 22.355 s]
[INFO] ignite-kubernetes .. SUCCESS [  2.073 s]
[INFO] ignite-zeromq .. SUCCESS [  2.446 s]
[INFO] ignite-rocketmq  SUCCESS [  6.950 s]
[INFO] ignite-hibernate_4.2 ... FAILURE [  2.575 s]
[INFO] ignite-hibernate_5.1 ... SKIPPED
[INFO] ignite-hibernate-core .. SKIPPED
[INFO] ignite-geospatial .. SKIPPED
[INFO] ignite-schedule  SKIPPED
[INFO] ignite-scalar 

Re: Hello

[Alexey Kuznetsov]

Hi, William!

I added you to contributors in JIRA.
Now you can assign IGNITE-5119 to your self.

Looking forward for your contribution.

FYI: https://ignite.apache.org/community/contribute.html#contribute


On Sat, Apr 29, 2017 at 5:15 PM, William Do  wrote:

> Hello everyone!
>
>
> I'd like to join the Ignite community and start contributing.
>
>
> May I have contributor access on JIRA? My JIRA ID is williamdo.
>
>
> I have raised an issue which I would like to work on.
>
>
> https://issues.apache.org/jira/browse/IGNITE-5119
>



-- 
Alexey Kuznetsov

Hello

[William Do]

Hello everyone!


I'd like to join the Ignite community and start contributing.


May I have contributor access on JIRA? My JIRA ID is williamdo.


I have raised an issue which I would like to work on.


https://issues.apache.org/jira/browse/IGNITE-5119

[jira] [Created] (IGNITE-5119) Provide more descriptive errors when calling affinityRun or affinityCall

[William Do (JIRA)]

William Do created IGNITE-5119:
--

 Summary: Provide more descriptive errors when calling affinityRun 
or affinityCall
 Key: IGNITE-5119
 URL: https://issues.apache.org/jira/browse/IGNITE-5119
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 1.9
Reporter: William Do
Priority: Minor


When calling compute affinityRun or affinityCall using a cache name that 
doesn't exist, an exception is thrown with the message: _Failed to get cache 
affinity_.

{noformat}
Exception in thread "main" class org.apache.ignite.IgniteException: Failed to 
get cache affinity.
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:946)
at 
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:201)
at 
com.ultimaspin.ignite.AffinityRunExample.main(AffinityRunExample.java:28)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to get cache 
affinity.
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition0(GridAffinityProcessor.java:192)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:175)
at 
org.apache.ignite.internal.processors.affinity.GridAffinityProcessor.partition(GridAffinityProcessor.java:155)
at 
org.apache.ignite.internal.IgniteComputeImpl.affinityCall(IgniteComputeImpl.java:191)
... 1 more
{noformat}

It would be nice if the message could give a more descriptive message as to why 
it was unable to determine the affinity (in this case because the cache doesn't 
exist).



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