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