Re: Apache Arrow and Apache Ignite

[Konstantin Boudnik]

On Fri, Feb 26, 2016 at 09:22PM, Dood@ODDO wrote:
> 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").

See, I too time to educate you on a variety of topics and provided you with
the pointers for future reading. How polite is that?

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

dev@ lists are indeed open for everyone. If you email to
dev-subscribe@arrow.a.o hasn't been answered, try once again - sometimes
emails get dropped. You also can write to dev-owner@arrow.a.o and let them
know, that your request wasn't addressed. 

Cos


signature.asc
Description: Digital signature

[GitHub] ignite pull request: Ignite 2718: Missing ZookeeperIpFinder depend...

[shroman]

GitHub user shroman opened a pull request:

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

Ignite 2718: Missing ZookeeperIpFinder dependencies



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

$ git pull https://github.com/shroman/ignite ignite-2718

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

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


commit 51f9538360156d0c6d7767c97dd62e5b9fae868f
Author: shtykh_roman 
Date:   2016-02-26T06:02:39Z

IGNITE-2718: Added Zookeeper IP finder dependencies.

commit 431a36999ac798acb1c7c8b9128b84f1384d03d8
Author: shtykh_roman 
Date:   2016-02-29T01:22:19Z

IGNITE-2718: Added Zookeeper IP finder dependencies. Removed ZK exclusions.




---
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: comm balance debug

[yzhdanov]

GitHub user yzhdanov opened a pull request:

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

comm balance debug



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

$ git pull https://github.com/yzhdanov/ignite comm-balance-debug-1.6

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

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


commit d25741ad0f0eef74e0807699f214790351f19280
Author: Yakov Zhdanov 
Date:   2016-02-28T22:26:42Z

comm balance debug




---
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: Creating client caches if 'schema not found' exception is thrown

[Valentin Kulichenko]

Sergi,

That's a good point, thanks. I will double-check this.

-Val

On Sat, Feb 27, 2016 at 12:04 PM, Sergi Vladykin 
wrote:

> Val,
>
> I didn't look at the code but I hope you've covered case when schema name
> is configured to be different from the cache name?
>
> Sergi
>
> 2016-02-27 2:34 GMT+03:00 Alexey Goncharuk :
>
> > Looks good to me.
> >
>

[GitHub] ignite pull request: ignite-2719 Value is not copied in entry proc...

[agura]

GitHub user agura opened a pull request:

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

ignite-2719 Value is not copied in entry processor

Fix for https://issues.apache.org/jira/browse/IGNITE-2719

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

$ git pull https://github.com/agura/incubator-ignite ignite-2719

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

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


commit 0079e966cd706d9fdb0b558ba706c3eb70bc9a2f
Author: agura 
Date:   2016-02-28T16:43:58Z

ignite-2719 Value is not copied in entry processor




---
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-2730) Ignite Events Source Streaming to Kafka

[Roman Shtykh (JIRA)]

Roman Shtykh created IGNITE-2730:


 Summary: Ignite Events Source Streaming to Kafka
 Key: IGNITE-2730
 URL: https://issues.apache.org/jira/browse/IGNITE-2730
 Project: Ignite
  Issue Type: New Feature
Reporter: Roman Shtykh
Assignee: Roman Shtykh


Streaming specified Ignite events (https://apacheignite.readme.io/docs/events) 
to Kafka via Kafka Connect.



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