Re: Apache Arrow and Apache Ignite

[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 conversation going. We want to be ahead of
the curve, not behind it - Arrow seems to be making quite a stir,
not to mention that it was fast-tracked to mature project status
apparently solely based on the people/companies involved ;-)

I am afraid you misunderstand the point of the 'fast tracking'. To start with,
ASF doesn't case what companies are involved nor there's no such thing as fast
tracking. However, there's 'direct to TLP' track, that allows for a community
that has enough ASF members and other people, with lengthy involvement into
Apache projects, to go directly into TLP. The reason is simple: these people
are well versed in Apache Way and the incubation isn't required for me.

So, please stop using this 'fast-tracked' confusion.
   Cos

P.S. Another point: TLP != 'mature project status'. Please educate yourself
about the Apache incubation, before making statement like this in the future.


I will educate myself. What you need to do is learn to be polite. I
am not sure you can teach that though ;(

If you don't mind elaborating on what particularly was impolite in my email, 
you'll
put me forever into your debts. And teach me a lesson of good manners too.

Cos
I don't know, you just came off as angered by what I said. You took the 
time to supposedly educate me how "fast tracking" is not the same as " 
taking a project directly to TLP" (which I think is obviously the same 
as fast tracking since it skipped the incubating phase). Then you took 
more time to educate me how people/companies are not what Apache looked 
at when fast tracking this project (pardon, taking the route called 
"direct to TLP") but you said that people experienced in the ways of 
Apache are what allowed for this project to be fast tracked (pardon 
again, taken "direct to TLP").


Incidentally, who can join the dev list on the Arrow project at this 
stage? I tried a week ago and was unsuccessful. I was under the 
impression that anyone can join it.

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

[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 in branch 'ignite-2455'? I will merge them to
master after TC passes.

[1] https://issues.apache.org/jira/browse/IGNITE-2455

-Val

Re: Deprecate IgniteConfiguration.getGridName

[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 not is defined by discovery
configuration:
https://apacheignite.readme.io/docs/cluster-config#isolated-ignite-clusters-on-the-same-set-of-machin

-Val

On Fri, Feb 26, 2016 at 7:19 AM, bintisepaha  wrote:

> 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/Deprecate-IgniteConfiguration-getGridName-tp2420p7613.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>

Re: Deprecate IgniteConfiguration.getGridName

[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/Deprecate-IgniteConfiguration-getGridName-tp2420p7613.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[GitHub] ignite pull request: Time sampling

[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 you can review and apply these changes as the patch at:

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


commit bac83051c7584da9a8004fc3753bbf9ea21d7594
Author: Ilya Lantukh 
Date:   2016-02-25T11:18:00Z

Optimizations.

commit 2e62b7840fa4139494476946ff2622330203707c
Author: Ilya Lantukh 
Date:   2016-02-25T14:43:56Z

FutVer optimization.

commit ee4ef4882c23b1cb323887140c5aef82a9ce8a34
Author: Ilya Lantukh 
Date:   2016-02-25T14:56:18Z

DHT request - removed unnecessary fields.

commit cf404ac90cca57218906dbb9d7724557f3c46d6e
Author: Ilya Lantukh 
Date:   2016-02-25T15:02:22Z

Temporary disabled message size metrics.

commit fec6d5fb1b19d89011e93689a839a99a10cf0b36
Author: Ilya Lantukh 
Date:   2016-02-26T12:07:41Z

Time sampling.

commit 5ee215a4dbcf1ac621e3a8b0a3d85bb7302daa74
Author: Ilya Lantukh 
Date:   2016-02-26T13:09:17Z

IO time sampling.

commit ff80e23be037ed0e7b51c8c05546b12b9f49b036
Author: Ilya Lantukh 
Date:   2016-02-26T13:44:39Z

IO response time sampling.

commit 02fa3aa6f15d51883a08fdacfea263c4ca042c04
Author: Ilya Lantukh 
Date:   2016-02-26T14:10:05Z

Time sampling thread.

commit 1a362fca758044b3cfd574c3b9fa9fc5d0656111
Author: Ilya Lantukh 
Date:   2016-02-26T14:12:04Z

Time sampling thread.




---
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-2729) .NET: Add Troubleshooting section to the documentation

[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
  Issue Type: Task
  Components: platforms
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6


Describe common issues and error messages (like "ClassNotFound", IGNITE_HOME 
issues, x64/x86 JVM, etc), and how to fix them.



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