[jira] [Created] (IGNITE-2398) .NET: Change default mapper behavior.

Vladimir Ozerov created IGNITE-2398: --- Summary: .NET: Change default mapper behavior. Key: IGNITE-2398 URL: https://issues.apache.org/jira/browse/IGNITE-2398 Project: Ignite Issue Type:

[GitHub] ignite pull request: IGNITE-1788: duplicate checking is removed.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/221 --- 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

[GitHub] ignite pull request: ignite-1923 Test fixed

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/408 ignite-1923 Test fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-1923 Alternatively you can review and apply

[jira] [Created] (IGNITE-2397) JDBC SQL Exceptions swallowed in case of not valid SQL query

Alexey Kuznetsov created IGNITE-2397: Summary: JDBC SQL Exceptions swallowed in case of not valid SQL query Key: IGNITE-2397 URL: https://issues.apache.org/jira/browse/IGNITE-2397 Project: Ignite

[GitHub] ignite pull request: IGNITE-2166 .NET: Add toBuilder() method on B...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/379 --- 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

[GitHub] ignite pull request: IGNITE-1514 Platform .Net: Implement IIgnite....

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/375 --- 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

[GitHub] ignite pull request: IGNITE-1901: Adopted new marshalling flags.

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/230 --- 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

[GitHub] ignite pull request: IGNITE-1413 .Net: Get rid of set -> map conve...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/380 --- 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

[jira] [Created] (IGNITE-2396) Dynamic cache changes are not tracked by service processor

Alexey Goncharuk created IGNITE-2396: Summary: Dynamic cache changes are not tracked by service processor Key: IGNITE-2396 URL: https://issues.apache.org/jira/browse/IGNITE-2396 Project: Ignite

[GitHub] ignite pull request: IGNITE-2043 .Net: ServiceExample has incorrec...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/296 --- 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

[GitHub] ignite pull request: IGNITE-2228 .Net: Ensure async Task can be ca...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/394 --- 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

Re: TcpDiscoverySpi.setLocalPortRange, value must be > 0

Hi, Thank for pointing out to this issue. Local port range set to 0 presently doesn't work at least for TcpCommunicationSpi and TcpDiscoverySpi. However SPIs support it. In my understanding the condition has to changed to the following one (from < to <=). x = port; x*<=* port + range

Re: about AOP development

Hi： I have already opened the peerClassLoading. My practice is in eclipse create a java project, developed a ComputeTaskSplitAdapter examples, then in the ComputeJobAdapter call configured spring interceptors service. This example in eclipse operation is no problem. But if I open a node in

Re: Semaphore action

I like the idea. Couple of comments though. I would leave only IgniteFuture acquireAndExecute(Callable action); Overload with executor can be omitted because callable implementation can use any executor. As far as moving acquire logic to another thread pool - I think we'd better go without it

Re: about AOP development

Can you please try enabling "peerClassLoading" and share the results here? --Yakov 2016-01-16 12:09 GMT+03:00 李玉珏@163 <18624049...@163.com>: > Hi： > > In a distributed environment, if use the spring AOP programming, generated > a class of byte code enhancement, then the error will be reported

[GitHub] ignite pull request: Refactored future adapter

GitHub user yzhdanov opened a pull request: https://github.com/apache/ignite/pull/409 Refactored future adapter You can merge this pull request into a Git repository by running: $ git pull https://github.com/yzhdanov/ignite jdk8-fut Alternatively you can review and apply

Re: GridFutureAdapter: deprecate startTime(), duration() and endTime()

Here is the PR https://github.com/apache/ignite/pull/409 - not ready to merge, but cache full api suite passes, so I can run distributed benchmarks tomorrow. Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2016-01-16 19:04 GMT+03:00 Dmitriy Setrakyan

[jira] [Created] (IGNITE-2399) Add asynchronous acquire to IgniteSemaphore

Vladisav Jelisavcic created IGNITE-2399: --- Summary: Add asynchronous acquire to IgniteSemaphore Key: IGNITE-2399 URL: https://issues.apache.org/jira/browse/IGNITE-2399 Project: Ignite

Re: Semaphore action

I created a ticket from this discussion: https://issues.apache.org/jira/browse/IGNITE-2399 Can someone please review it (and edit if needed)? Best regrads, VJ On Mon, Jan 18, 2016 at 12:28 PM, Yakov Zhdanov wrote: > I like the idea. Couple of comments though. > > I would

Re: Marking fixed JIRAs against releases

Cos, to my knowledge, the release notes are generated by searching for a fix version, so the tickets you are pointing out will likely be missed. Generally speaking all fixed tickets should have a fix version. Let’s make sure that we follow this rule going forward. (Any way to enforce it?) D. On

Marking fixed JIRAs against releases

Guys, as a fall-out from another conversation I've ran the following search on JIRA project = ignite and status in (Fixed, Closed) and fixVersion is null and we have 150 (yes, some of them are dups and won't fixes) closed/fixed tickets without explicit fixVersion on them. How do we keep