Austin Sharp <austins...@...>
Hi all,
I am pretty excited about the things getting merged into JanusGraph. In particular I really want to get my hands on the new CQL storage backend and the updated ElasticSearch indexing backend, since it'll take us a fair amount of work to get those integrated (i.e. upgrading existing installations of Cassandra and ES to much newer versions). In fact, we have logged bugs that get more or less instantly fixed by an upgrade.
So this leads me to ask: what's the plan for JanusGraph 0.2.0? As a Cassandra + ES user I feel like rewrites of both of those drivers is a pretty big deal, but those using other backends may feel differently. What's important to me is to have a timeline on when to expect the CQL + ES backends to be released, since if we don't get those in a certain time frame it'll mean finding ways to work around the problem.
|
|
Jason Plurad <plu...@...>
You're right, I think the Cassandra and Elasticsearch bumps are the major items for the next release. In mid-June there will be another TinkerPop release 3.2.5. I think it would be good to align a JanusGraph release relatively soon after that. One item I want to get more focus on is which version of Spark to support or if we need to support multiple versions. If there are folks out there already doing Spark OLAP, what version are you using? Currently 1.6.1 is the supported version, but there are more recent versions available, and I'm not sure how easy it would be to support 2.0.x and 2.1.x. Solr might need a bump -- any Solr folks out there want to chime in?
toggle quoted message
Show quoted text
On Wednesday, May 24, 2017 at 11:17:50 AM UTC-4, Austin Sharp wrote: Hi all,
I am pretty excited about the things getting merged into JanusGraph. In particular I really want to get my hands on the new CQL storage backend and the updated ElasticSearch indexing backend, since it'll take us a fair amount of work to get those integrated (i.e. upgrading existing installations of Cassandra and ES to much newer versions). In fact, we have logged bugs that get more or less instantly fixed by an upgrade.
So this leads me to ask: what's the plan for JanusGraph 0.2.0? As a Cassandra + ES user I feel like rewrites of both of those drivers is a pretty big deal, but those using other backends may feel differently. What's important to me is to have a timeline on when to expect the CQL + ES backends to be released, since if we don't get those in a certain time frame it'll mean finding ways to work around the problem.
|
|
Samik Raychaudhuri <sam...@...>
toggle quoted message
Show quoted text
You're right, I think the Cassandra and
Elasticsearch bumps are the major items for the next release.
In mid-June
there will be another TinkerPop release 3.2.5. I think it would
be good to align a JanusGraph release relatively soon after
that.
One item I want to get more focus on is which
version of Spark to support or if we need to support
multiple versions. If there are folks out there already doing
Spark OLAP, what version are you using? Currently 1.6.1 is the
supported version, but there are more recent versions available,
and I'm not sure how easy it would be to support 2.0.x and
2.1.x.
Solr might need a bump -- any Solr folks out there want to chime
in?
On Wednesday, May 24, 2017 at 11:17:50 AM UTC-4, Austin Sharp
wrote:
Hi all,
I am pretty excited about the things getting merged into
JanusGraph. In particular I really want to get my hands on
the new CQL storage backend and the updated ElasticSearch
indexing backend, since it'll take us a fair amount of work
to get those integrated (i.e. upgrading existing
installations of Cassandra and ES to much newer versions).
In fact, we have logged bugs that get more or less instantly
fixed by an upgrade.
So this leads me to ask: what's the plan for JanusGraph
0.2.0? As a Cassandra + ES user I feel like rewrites of both
of those drivers is a pretty big deal, but those using other
backends may feel differently. What's important to me is to
have a timeline on when to expect the CQL + ES backends to
be released, since if we don't get those in a certain time
frame it'll mean finding ways to work around the problem.
--
You received this message because you are subscribed to the Google
Groups "JanusGraph developer list" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to janusgr...@....
For more options, visit https://groups.google.com/d/optout.
|
|
It is a good plan from Jason.
For the Spark support, based on the discussion link, it does not seem to be likely the Spark 2.x support will be back-ported to Tinkerpop 3.2.x. Without Tinkerpop 3.3, we will have to live with Spark 1.6.1 for now in JanusGraph?
Thanks.
Jerry
toggle quoted message
Show quoted text
On Saturday, May 27, 2017 at 8:03:19 AM UTC-7, Samik R wrote:
I recently tried using Spark 2.1.0 branch with
Janusgraph for OLAP queries. Essentially, that entailed trying to
compile spark-gremlin with Spark 2.1.0. I progressed a bit, but at
the end, I was unable to successfully compile because of complex
dependency structure.
I am not sure what is TP's plan for upgrading the version of
spark. I wrote a post regarding that in the email list
[https://groups.google.com/d/msgid/gremlin-users/1fd7a282-b18a-4b99-a436-f8448b1d7fe7%40googlegroups.com?utm_medium=email&utm_source=footer]
but Stephen replied saying he is not aware of any plans.
In the end I reverted to using spark 1.6.1.
Regards,
-Samik
On 26-May-17 8:38 PM, Jason Plurad
wrote:
You're right, I think the Cassandra and
Elasticsearch bumps are the major items for the next release.
In mid-June
there will be another TinkerPop release 3.2.5. I think it would
be good to align a JanusGraph release relatively soon after
that.
One item I want to get more focus on is which
version of Spark to support or if we need to support
multiple versions. If there are folks out there already doing
Spark OLAP, what version are you using? Currently 1.6.1 is the
supported version, but there are more recent versions available,
and I'm not sure how easy it would be to support 2.0.x and
2.1.x.
Solr might need a bump -- any Solr folks out there want to chime
in?
On Wednesday, May 24, 2017 at 11:17:50 AM UTC-4, Austin Sharp
wrote:
Hi all,
I am pretty excited about the things getting merged into
JanusGraph. In particular I really want to get my hands on
the new CQL storage backend and the updated ElasticSearch
indexing backend, since it'll take us a fair amount of work
to get those integrated (i.e. upgrading existing
installations of Cassandra and ES to much newer versions).
In fact, we have logged bugs that get more or less instantly
fixed by an upgrade.
So this leads me to ask: what's the plan for JanusGraph
0.2.0? As a Cassandra + ES user I feel like rewrites of both
of those drivers is a pretty big deal, but those using other
backends may feel differently. What's important to me is to
have a timeline on when to expect the CQL + ES backends to
be released, since if we don't get those in a certain time
frame it'll mean finding ways to work around the problem.
--
You received this message because you are subscribed to the Google
Groups "JanusGraph developer list" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to janusgraph-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
|
|
I think we'll need to stick with Spark 1.6.1 for now. Jason's plan also sounds good to me. The 3.2.5 TinkerPop bump should be pretty straightforward so we could probably target a late June, early July release for JanusGraph.
--Ted
toggle quoted message
Show quoted text
On Tuesday, May 30, 2017 at 2:00:59 PM UTC-5, Jerry He wrote: It is a good plan from Jason.
For the Spark support, based on the discussion link, it does not seem to be likely the Spark 2.x support will be back-ported to Tinkerpop 3.2.x. Without Tinkerpop 3.3, we will have to live with Spark 1.6.1 for now in JanusGraph?
Thanks.
Jerry On Saturday, May 27, 2017 at 8:03:19 AM UTC-7, Samik R wrote:
I recently tried using Spark 2.1.0 branch with
Janusgraph for OLAP queries. Essentially, that entailed trying to
compile spark-gremlin with Spark 2.1.0. I progressed a bit, but at
the end, I was unable to successfully compile because of complex
dependency structure.
I am not sure what is TP's plan for upgrading the version of
spark. I wrote a post regarding that in the email list
[https://groups.google.com/d/msgid/gremlin-users/1fd7a282-b18a-4b99-a436-f8448b1d7fe7%40googlegroups.com?utm_medium=email&utm_source=footer]
but Stephen replied saying he is not aware of any plans.
In the end I reverted to using spark 1.6.1.
Regards,
-Samik
On 26-May-17 8:38 PM, Jason Plurad
wrote:
You're right, I think the Cassandra and
Elasticsearch bumps are the major items for the next release.
In mid-June
there will be another TinkerPop release 3.2.5. I think it would
be good to align a JanusGraph release relatively soon after
that.
One item I want to get more focus on is which
version of Spark to support or if we need to support
multiple versions. If there are folks out there already doing
Spark OLAP, what version are you using? Currently 1.6.1 is the
supported version, but there are more recent versions available,
and I'm not sure how easy it would be to support 2.0.x and
2.1.x.
Solr might need a bump -- any Solr folks out there want to chime
in?
On Wednesday, May 24, 2017 at 11:17:50 AM UTC-4, Austin Sharp
wrote:
Hi all,
I am pretty excited about the things getting merged into
JanusGraph. In particular I really want to get my hands on
the new CQL storage backend and the updated ElasticSearch
indexing backend, since it'll take us a fair amount of work
to get those integrated (i.e. upgrading existing
installations of Cassandra and ES to much newer versions).
In fact, we have logged bugs that get more or less instantly
fixed by an upgrade.
So this leads me to ask: what's the plan for JanusGraph
0.2.0? As a Cassandra + ES user I feel like rewrites of both
of those drivers is a pretty big deal, but those using other
backends may feel differently. What's important to me is to
have a timeline on when to expect the CQL + ES backends to
be released, since if we don't get those in a certain time
frame it'll mean finding ways to work around the problem.
--
You received this message because you are subscribed to the Google
Groups "JanusGraph developer list" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to janusgraph-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
|
|
Samik Raychaudhuri <sam...@...>
As mentioned, I reverted back to spark 1.6.1
and it works pretty well. I think we can stick with 1.6.1 till we
move to TP 3.3, when that is available.
Regards,
-Samik
On 02-Jun-17 7:38 PM, Ted Wilmes wrote:
toggle quoted message
Show quoted text
I think we'll need to stick with Spark 1.6.1 for
now. Jason's plan also sounds good to me. The 3.2.5 TinkerPop
bump should be pretty straightforward so we could probably
target a late June, early July release for JanusGraph.
--Ted
|
|