Hello,
Here are notes to peoples comments thus far:
1. TinkerPop2 (prior to Apache) maintained all the vendor connectors.
This was very burdensome for the TinkerPop developers as we had to stay up to
date on each vendors changes. We didn't want to go down this road for
TinkerPop3 (now
+1 (binding) from my side for the release.
Thanks,
Amareshwari
On Thu, Apr 30, 2015 at 5:35 PM, Amareshwari Sriramdasu <
amareshw...@apache.org> wrote:
> Hello everyone,
>
> This is the call for vote for the following RC to be released as official
> ApacheLens 2.1.0-beta-incubating release. This
Hello everyone,
This is the call for vote for the following RC to be released as official
ApacheLens 2.1.0-beta-incubating release. This is our second release.
Apache Lens provides an Unified Analytics interface. Lens aims to cut the
Data Analytics silos by providing a single view of data across
Hi,
On Tue, Apr 28, 2015 at 5:33 PM, Marko Rodriguez wrote:
> ...In short, TinkerPop would depend on an Apache2 licensed neo4j-api. Some
> manual
> downloads from testers/users would be required to use the tinkerpop-neo4j
> component
> with a Neo4j database
That sounds ok to me as long as
On 30/04/2015 00:24, "Niclas Hedhman" wrote:
>But may I suggest the other way around?? Can't Neo4j have a Tinkerpop
>module at their end, which Tinkerpop advertise to be available for those
>that can live with the GPL/AGPL limitations? That would make this a
>non-issue, and IIUIC fits well withi
