[GitHub] ignite pull request: IGNITE-2621 .NET: Fix compute in mixed-platfo...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2752) LINQ NuGet package

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2752:
--

 Summary: LINQ NuGet package
 Key: IGNITE-2752
 URL: https://issues.apache.org/jira/browse/IGNITE-2752
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn


Since NuGet is merged, we should create a package for LINQ assembly, and 
include LINQPad samples in it.



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

[jira] [Created] (IGNITE-2750) REST connection is closed on the server side ignoring unfinished client requests

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2750:
---

 Summary: REST connection is closed on the server side ignoring 
unfinished client requests
 Key: IGNITE-2750
 URL: https://issues.apache.org/jira/browse/IGNITE-2750
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5.0.final
Reporter: Denis Magda
 Fix For: 1.6


Client can send long running request (i.e., compute tasks) to the cluster over 
REST connection. If a task execution takes more time than 
{{ConnectorConfiguration.idleTimeout}} then the connection will be closed by 
server automatically.

The server mustn't close the connection in cases if there are unfinished 
requests received from clients. This approach already works on the client side.



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

[jira] [Created] (IGNITE-2749) Web session clustering works incorrectly with WebLogic

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2749:
---

 Summary: Web session clustering works incorrectly with WebLogic
 Key: IGNITE-2749
 URL: https://issues.apache.org/jira/browse/IGNITE-2749
 Project: Ignite
  Issue Type: Bug
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Critical
 Fix For: 1.6


{{WebSessionFilter}} has a special processing for the session ID generated by 
WebLogic. The issue is that this processing is not applied in all required 
cases.  E.g., session ID is transformed when new session is saved in cache (see 
{{createSession}} method, but not transformed when it's fetched from cache (see 
{{doFilter0}}.

Need to go through the code, locate incorrect places and fix.



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

Re: Thief node does not belong to task topology [was "Failed to send message"]

[Valentin Kulichenko]

Hi Paolo,

See my comment in the ticket.

-Val

On Wed, Mar 2, 2016 at 2:04 AM, Paolo Di Tommaso 
wrote:

> Hi Val,
>
> I surely can contribute on that issue but I would need a fix as soon as
> possible so I will do both. Thus, I will try the dirty path on my own
> implementation and to implement a fix for IGNITE-1267
> .
>
> However also in the above issue the last comment suggests to remove the
> check on the task topology and I have any clue of any better alternative.
> Could you clarify how do you think it should be fixed?
>
>
> Cheers,
> Paolo
>
>
>
> On Tue, Mar 1, 2016 at 11:56 PM, vkulichenko <
> valentin.kuliche...@gmail.com>
> wrote:
>
> > Paolo,
> >
> > I found the ticket about this issue [1]. How about picking it up and
> fixing
> > instead of implementing your own version of the SPI?
> >
> > Removing the check completely is wrong, because it's possible that a node
> > doesn't belong to the cluster group on which the task was executed. But
> we
> > should check the original predicate instead of collection of nodes sealed
> > during the map phase.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-1267
> >
> > -Val
> >
> >
> >
> > --
> > View this message in context:
> >
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-send-message-tp3217p3317.html
> > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
> >
>

[jira] [Created] (IGNITE-2748) Service proxy makes remote call for methods declared in java.lang.Object

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2748:
---

 Summary: Service proxy makes remote call for methods declared in 
java.lang.Object
 Key: IGNITE-2748
 URL: https://issues.apache.org/jira/browse/IGNITE-2748
 Project: Ignite
  Issue Type: Bug
  Components: managed services
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Critical
 Fix For: 1.6


To reproduce the issue, get a service proxy and call one of 
{{java.lang.Object}}  methods (e.g., {{hashCode}}). It will make a remote call, 
which is not needed and can cause issues.



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

Re: Contributions that are waiting for review

[Denis Magda]

I would better ask contributors to ping committers on the dev list when 
a patch is available asking for review.
It can happen that committers missed or forgot to do the review and a 
contributor can remind them sending one more email to the dev list.


I don't see anything wrong with this approach. It's an open source 
project and most of the people don't keep an eye on new contributions 
that have to be released.


PATCH_AVAILABLE stat is a right point. But I won't execute this filter 
all the time checking for pending reviews and some of the committers 
don't move the ticket to the CLOSED state when everything is merged.

The latter was discussed some time ago there.

--
Denis

On 3/2/2016 6:02 PM, Anton Vinogradov wrote:

Denis,

We have a special status at Ignite JIRA - PATCH AVAILABLE which means that
issue ready to be reviewed.
Currently 59 issues has such status according to
https://issues.apache.org/jira/issues/?filter=-2=project%20%3D%20Ignite%20and%20status%20%3D%20%22Patch%20Available%22

I think we have to add notes that this status can be used only during
waiting of review and we will have no problems with actual "required
review" list in future.


On Wed, Mar 2, 2016 at 4:08 PM, Roman Shtykh 
wrote:


I have also asked for review of the following tickets but failed to get a
feedback.
They are not complicated, but I would appreciate a quick review. Thank you!

[IGNITE-2563] Queries: ArrayIndexOutOfBoundsException when using BOOL_AND

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

IGNITE-2416 TcpDiscoverySharedFsIpFinder doesn't work with IPv6 addresses
https://issues.apache.org/jira/browse/IGNITE-2416

and a new one

IGNITE-2710 Session not unbind from current request after invoking
request.getSession().invalidate()
https://issues.apache.org/jira/browse/IGNITE-2710

-Roman


On Wednesday, March 2, 2016 6:38 PM, Denis Magda 
wrote:



Ignite committers,

There is a number of contributions that have to be reviewed.

Please pick them up basing on your experience and provide your review
notes.

Ignite 2718: Missing ZookeeperIpFinder dependencies

IGNITE-2693: withKeepBinary and non-binary marshallers

IGNITE-2735: Fixes distributed semaphore local node stopping issue.

*IGNITE-642: Implements cache distributed reentrant lock



*Regards,
Denis

Re: Deprecate IgniteConfiguration.getGridName

[bintisepaha]

Thank you Val, this is very helpful.



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Deprecate-IgniteConfiguration-getGridName-tp2420p7685.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Contributions that are waiting for review

[Denis Magda]

Roman,

Please send the message directly to the dev list when you need a review. 
Quite often people who open an issue are not eligible for review and 
thus don't provide any feedback.


Regards,
Denis

On 3/2/2016 4:08 PM, Roman Shtykh wrote:

I have also asked for review of the following tickets but failed to get a 
feedback.
They are not complicated, but I would appreciate a quick review. Thank you!

[IGNITE-2563] Queries: ArrayIndexOutOfBoundsException when using BOOL_AND

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

IGNITE-2416 TcpDiscoverySharedFsIpFinder doesn't work with IPv6 addresses
https://issues.apache.org/jira/browse/IGNITE-2416

and a new one

IGNITE-2710 Session not unbind from current request after invoking 
request.getSession().invalidate()
https://issues.apache.org/jira/browse/IGNITE-2710

-Roman


On Wednesday, March 2, 2016 6:38 PM, Denis Magda  wrote:



Ignite committers,

There is a number of contributions that have to be reviewed.

Please pick them up basing on your experience and provide your review notes.

Ignite 2718: Missing ZookeeperIpFinder dependencies

IGNITE-2693: withKeepBinary and non-binary marshallers

IGNITE-2735: Fixes distributed semaphore local node stopping issue.

*IGNITE-642: Implements cache distributed reentrant lock



*Regards,
Denis

[jira] [Created] (IGNITE-2747) ODBC: Time cast returns wrong results for Linux.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-2747:
---

 Summary: ODBC: Time cast returns wrong results for Linux.
 Key: IGNITE-2747
 URL: https://issues.apache.org/jira/browse/IGNITE-2747
 Project: Ignite
  Issue Type: Sub-task
  Components: odbc
Affects Versions: 1.5.0.final
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


Current time cast does not work for Linux because {{timezone}} variable does 
not return right time offset for Linux.

Also, {{gmtime}} is not thread-safe so it seems that we should use some 
platform-specific functions for time-conversion operations.



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

[GitHub] ignite pull request: IGNITE-2333

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: ignite-2734 Binary enum type deserialization ...

[agura]

Github user agura closed the pull request at:

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


---
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: Contributions that are waiting for review

[Anton Vinogradov]

Denis,

We have a special status at Ignite JIRA - PATCH AVAILABLE which means that
issue ready to be reviewed.
Currently 59 issues has such status according to
https://issues.apache.org/jira/issues/?filter=-2=project%20%3D%20Ignite%20and%20status%20%3D%20%22Patch%20Available%22

I think we have to add notes that this status can be used only during
waiting of review and we will have no problems with actual "required
review" list in future.


On Wed, Mar 2, 2016 at 4:08 PM, Roman Shtykh 
wrote:

> I have also asked for review of the following tickets but failed to get a
> feedback.
> They are not complicated, but I would appreciate a quick review. Thank you!
>
> [IGNITE-2563] Queries: ArrayIndexOutOfBoundsException when using BOOL_AND
>
> https://issues.apache.org/jira/browse/IGNITE-2563
>
> IGNITE-2416 TcpDiscoverySharedFsIpFinder doesn't work with IPv6 addresses
> https://issues.apache.org/jira/browse/IGNITE-2416
>
> and a new one
>
> IGNITE-2710 Session not unbind from current request after invoking
> request.getSession().invalidate()
> https://issues.apache.org/jira/browse/IGNITE-2710
>
> -Roman
>
>
> On Wednesday, March 2, 2016 6:38 PM, Denis Magda 
> wrote:
>
>
>
> Ignite committers,
>
> There is a number of contributions that have to be reviewed.
>
> Please pick them up basing on your experience and provide your review
> notes.
>
> Ignite 2718: Missing ZookeeperIpFinder dependencies
> 
> IGNITE-2693: withKeepBinary and non-binary marshallers
> 
> IGNITE-2735: Fixes distributed semaphore local node stopping issue.
> 
> *IGNITE-642: Implements cache distributed reentrant lock
> 
>
>
> *Regards,
> Denis
>

Re: Contributions that are waiting for review

[Roman Shtykh]

I have also asked for review of the following tickets but failed to get a 
feedback.
They are not complicated, but I would appreciate a quick review. Thank you!

[IGNITE-2563] Queries: ArrayIndexOutOfBoundsException when using BOOL_AND

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

IGNITE-2416 TcpDiscoverySharedFsIpFinder doesn't work with IPv6 addresses
https://issues.apache.org/jira/browse/IGNITE-2416

and a new one

IGNITE-2710 Session not unbind from current request after invoking 
request.getSession().invalidate()
https://issues.apache.org/jira/browse/IGNITE-2710

-Roman


On Wednesday, March 2, 2016 6:38 PM, Denis Magda  wrote:



Ignite committers,

There is a number of contributions that have to be reviewed.

Please pick them up basing on your experience and provide your review notes.

Ignite 2718: Missing ZookeeperIpFinder dependencies 

IGNITE-2693: withKeepBinary and non-binary marshallers 

IGNITE-2735: Fixes distributed semaphore local node stopping issue. 

*IGNITE-642: Implements cache distributed reentrant lock 



*Regards,
Denis

[jira] [Created] (IGNITE-2746) .NET: Improve ReflectiveSerializer control with attributes

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2746:
--

 Summary: .NET: Improve ReflectiveSerializer control with attributes
 Key: IGNITE-2746
 URL: https://issues.apache.org/jira/browse/IGNITE-2746
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
Priority: Minor
 Fix For: 1.6


Allow custom field names and ordering (similar to DataMemberAttribute, for 
example: 
https://msdn.microsoft.com/en-us/library/system.runtime.serialization.datamemberattribute(v=vs.110).aspx)



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

[GitHub] ignite pull request: Ignite 2191 Not to merge

[ashutakGG]

Github user ashutakGG closed the pull request at:

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


---
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: IGNITE-2740 Remove error in IGNITE_HOME check

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-2740 Remove error in IGNITE_HOME check



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

$ git pull https://github.com/ptupitsyn/ignite ignite-2740

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

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


commit 917051798822aec2afe03cf0c121766732bd0471
Author: Pavel Tupitsyn 
Date:   2016-03-02T10:43:32Z

Remove forced IGNITE_HOME check




---
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: Ignite-2191 Experiment (not to merge)

[ashutakGG]

Github user ashutakGG closed the pull request at:

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


---
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-2745) Fast access to GridTopic listeners.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2745:
---

 Summary: Fast access to GridTopic listeners.
 Key: IGNITE-2745
 URL: https://issues.apache.org/jira/browse/IGNITE-2745
 Project: Ignite
  Issue Type: Sub-task
  Components: general
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 1.6


Currently all listeners are located inside a ConcurrentHashMap. It takes some 
time to get a listener from it.

The most important listeners are those of GridTopic enum. Let's store these 
listeners in volatile array where enum ordinal will be listener index.



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

[jira] [Created] (IGNITE-2744) Optimize "unwindEvict" call in GridCacheIoManager.processMessage().

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2744:
---

 Summary: Optimize "unwindEvict" call in 
GridCacheIoManager.processMessage().
 Key: IGNITE-2744
 URL: https://issues.apache.org/jira/browse/IGNITE-2744
 Project: Ignite
  Issue Type: Sub-task
  Components: cache
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: 1.6


We call this method on every (!!!) received cache message. This call is pretty 
heavy as it iterates over all caches. 
We need to optimize it. E.g., check evicts only for the cache to which received 
message belongs. And iterate over the whole set only if we know for sure that 
several caches are affected (e.g. due to cross-cache TX).



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

[jira] [Created] (IGNITE-2743) Broken download page on ignite.apache.org

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2743:
--

 Summary: Broken download page on ignite.apache.org
 Key: IGNITE-2743
 URL: https://issues.apache.org/jira/browse/IGNITE-2743
 Project: Ignite
  Issue Type: Bug
  Components: website
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
Priority: Blocker
 Fix For: 1.6


There are two download pages:
* https://ignite.apache.org/download.cgi (correct)
* https://ignite.apache.org/download (incorrect)

All links are broken on the second one. You can't get on this broken page from 
our website, but it is the first page in Google for "apache ignite download": 
https://www.google.ru/search?q=apache+ignite+download

Ideally, https://ignite.apache.org/download should be the correct link (.cgi in 
the url is from 90's)



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

Re: Multimap implementation attempt

[Yakov Zhdanov]

Hi Konstantin!

I have added a comment to the ticket.

--Yakov

2016-03-01 16:13 GMT+03:00 Konstantin Margorin :

> Hello Igniters.
>
> I'm trying now to implement Multimap datastructure. I wrote a comment about
> implementation details here:
>
> https://issues.apache.org/jira/browse/IGNITE-640
>
> Now I got Multimap prototype with put/get methods:
>
>
> https://github.com/apache/ignite/compare/master...ruskim:ignite-640?expand=1
>
> This basic test for put/get successfully passed:
>
>
> https://github.com/ruskim/ignite/blob/2af6274f9234dda1550696014ffd8e327d75da57/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/datastructures/GridCacheMultimapSelfTest.java
>
> A lot of thing I did by analogy with IgniteQueue and IgniteSet. I realize,
> that most probably I made a lot of errors.
>
> Before moving further I want to be sure that basic things, like put/get,
> implemented properly.
>
> Probably someone could look at my code and point me at most serious errors.
>
> Thank you!
>
> Konstantin
>

[jira] [Created] (IGNITE-2742) Do not save "confirm" and "agree" on user sign up

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2742:
--

 Summary: Do not save "confirm" and "agree" on user sign up
 Key: IGNITE-2742
 URL: https://issues.apache.org/jira/browse/IGNITE-2742
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov
Priority: Minor


Current save request contains "confirm":"1","agree":true.
No needs to save these parameters to the DB.



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

[GitHub] ignite pull request: Fix for jCache TCK

[ashutakGG]

Github user ashutakGG closed the pull request at:

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


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

Contributions that are waiting for review

[Denis Magda]

Ignite committers,

There is a number of contributions that have to be reviewed.

Please pick them up basing on your experience and provide your review notes.

Ignite 2718: Missing ZookeeperIpFinder dependencies 

IGNITE-2693: withKeepBinary and non-binary marshallers 

IGNITE-2735: Fixes distributed semaphore local node stopping issue. 

*IGNITE-642: Implements cache distributed reentrant lock 




*Regards,
Denis