[jira] [Created] (IGNITE-2729) .NET: Add Troubleshooting section to the documentation

2016-02-26 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-2729: -- Summary: .NET: Add Troubleshooting section to the documentation Key: IGNITE-2729 URL: https://issues.apache.org/jira/browse/IGNITE-2729 Project: Ignite I

[GitHub] ignite pull request: Ignite 2715

2016-02-26 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/514 --- 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 enab

[GitHub] ignite pull request: Time sampling

2016-02-26 Thread ilantukh
GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/517 Time sampling Only for benchmarking. Do not merge. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite TimeSampling Alternatively y

[GitHub] ignite pull request: IGNITE-2700

2016-02-26 Thread ilantukh
GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/518 IGNITE-2700 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2700 Alternatively you can review and apply these ch

[GitHub] ignite pull request: IGNITE-642: Implements cache distributed reen...

2016-02-26 Thread vladisav
GitHub user vladisav opened a pull request: https://github.com/apache/ignite/pull/519 IGNITE-642: Implements cache distributed reentrant lock You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladisav/ignite ignite-642 Alternative

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

2016-02-26 Thread Vladisav Jelisavcic
Hi, i recently implemented distributed ReentrantLock - IGNITE-642, i made a pull request, so hopefully this could be added to the next release. Best regards, Vladisav On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Folks, > > The current implementation

Re: Deprecate IgniteConfiguration.getGridName

2016-02-26 Thread bintisepaha
Hi, We are facing this issue, nodes with different grid names are being identified in a single topology. Did the fix for this make it into version 1.6? If yes, how can I get this version? Thanks, Binti -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Depr

Re: Deprecate IgniteConfiguration.getGridName

2016-02-26 Thread Valentin Kulichenko
Binti, This is not an issue. What is discussed here is just proper naming of this configuration property, but the concept stays the same - this is the name of local Ignite instance and there is no requirement for all nodes in topology to share the same name. Whether nodes discover each other or n

Creating client caches if 'schema not found' exception is thrown

2016-02-26 Thread Valentin Kulichenko
Folks, We have a pretty serious issue [1] that potentially breaks cross-cache queries in JDBC driver and in other integrations like Zeppelin interpreter, Spark, etc. I made a simple fix - catch the exception and create all client caches that are currently missing. Can someone review my changes i

Re: Creating client caches if 'schema not found' exception is thrown

2016-02-26 Thread Alexey Goncharuk
Looks good to me.

Re: Apache Arrow and Apache Ignite

2016-02-26 Thread Dood
On 2/25/2016 11:06 AM, Konstantin Boudnik wrote: On Wed, Feb 24, 2016 at 02:02PM, Dood@ODDO wrote: On 2/24/2016 1:31 PM, Konstantin Boudnik wrote: On Sat, Feb 20, 2016 at 02:13PM, Dood@ODDO wrote: That's the million dollar question - I think we should approach the Arrow people and get a conver