Date   

What's the plan for the next release?

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.


Re: [DISCUSS] Travis builds and PR testing

Ted Wilmes <twi...@...>
 

I'm okay with continuing to require the additional modules. You guys have made a lot of progress on test stability and this will keep that at the forefront.

Thanks,
Ted


On Sunday, May 21, 2017 at 9:15:24 PM UTC-5, sjudeng wrote:
Now that #251 has been merged tests in all modules except hbase-098 and cql are required to pass for a successful Travis build. However since merging there have been more unexpected build failures than were observed during testing as part of that PR. The open #279 should resolve some of these failures but it's likely there will still be some unexpected failures of Travis jobs.

Are there concerns/comments regarding continuing to require the additional modules to pass for a successful Travis build (and PR merge)? In the case of unexpected failures committers can login to Travis and restart the failed job(s) without restarting the entire build (see attached). While this is not automatic I think it's still easier than requiring PR reviewers to run tests locally or request test summaries from contributors and it also keeps these test checks more public.


[DISCUSS] Travis builds and PR testing

sjudeng <sju...@...>
 

Now that #251 has been merged tests in all modules except hbase-098 and cql are required to pass for a successful Travis build. However since merging there have been more unexpected build failures than were observed during testing as part of that PR. The open #279 should resolve some of these failures but it's likely there will still be some unexpected failures of Travis jobs.

Are there concerns/comments regarding continuing to require the additional modules to pass for a successful Travis build (and PR merge)? In the case of unexpected failures committers can login to Travis and restart the failed job(s) without restarting the entire build (see attached). While this is not automatic I think it's still easier than requiring PR reviewers to run tests locally or request test summaries from contributors and it also keeps these test checks more public.


Re: Deprecation warnings using elasticsearch 5.1.1

Nigel Brown <ni...@...>
 

Thanks, that is what I thought.

For what it is worth, I think you should initially prefer the newer versions as janusgraph is new.


Re: Deprecation warnings using elasticsearch 5.1.1

sjudeng <sju...@...>
 

Yes this is expected. The Elasticsearch 5.x REST API is backwards compatible with Elasticsearch 2.x. JanusGraph is leveraging this, which means separate modules/profiles are not required for ES 2.x/5.x compatibility. But the disadvantage is the deprecation warnings.

I've been meaning to start a discussion on next steps for ES. I wanted to propose we consider migrating from using the ES QueryBuilders/Settings API to manually building the request objects. Among other things I think this would make it easy to add compatibility shims for ES versions to resolve deprecation warnings and maybe more importantly take advantage of any new features of interest in newer versions, without requiring separate modules/profiles.


[WARNING] 0.1.0 to 0.1.1 upgrade

Ted Wilmes <twi...@...>
 

Hello,
A step was missed during the release prep and the 0.1.1 release was not marked as compatible with JanusGraph 0.1.0. Consequently, if you point 0.1.1 at a previously loaded 0.1.0 backend (not Titan), JanusGraph will not start and you'll get: 

"StorageBackend version is incompatible with current JanusGraph version: storage [0.1.0] vs. runtime [0.1.1]"

The backend format is not really incompatible and an issue has been entered to address this [1].

The 0.1.1 release mainly fixes a serious Titan compatibility issue [2] and if you are upgrading from Titan, you will not be affected by this incompatibility error and can upgrade because Janus is correctly marked as compatible with Titan 1.0 and Titan 1.1-SNAPSHOT.

If you are running 0.1.0 right now from a brand new JanusGraph load (not an upgrade from Titan), hold off on upgrading until this issues is taken care of. If you planned on rebuilding your data from scratch when upgrading to 0.1.1, you can go ahead and upgrade as this only affects a previously loaded system.

Thanks,
Ted


Re: New TSC member: sjudeng

Ted Wilmes <twi...@...>
 

Awesome news and congrats sjudeng!


On Tuesday, May 16, 2017 at 11:53:45 AM UTC-5, Jerry He wrote:
Congrats, sjudeng!


Jerry

On Mon, May 15, 2017 at 11:01 AM, Jason Plurad <plu...@...> wrote:
The Technical Steering Committee (TSC) for JanusGraph is pleased to welcome sjudeng as a TSC member on the project (effective May 10). sjudeng has provided major contributions and has demonstrated an on-going commitment to the project in these initial months. Being a TSC member enables assistance with the project management and to guide the direction of the project.

Congratulations to sjudeng and we're looking forward to building up the JanusGraph community with you!

--
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-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Deprecation warnings using elasticsearch 5.1.1

Nigel Brown <ni...@...>
 

Hello;
I was using the code in the master, specifically to test the excellent https://github.com/JanusGraph/janusgraph/issues/67. It all seems to be working, but on startup, where I create the indices, I see the following warnings

13:07:31.152 [I/O dispatcher 1] WARN  org.elasticsearch.client.RestClient - request [PUT http://localhost:9200/janusgraph/_mapping/mixedE] returned 1 warnings: [The [string] field is deprecated, please us

e [text] or [keyword] instead on [event_name]]

13:07:33.212 [I/O dispatcher 1] WARN  org.elasticsearch.client.RestClient - request [PUT http://localhost:9200/janusgraph/_mapping/identity_usernameTextKey] returned 1 warnings: [The [string] field is dep

recated, please use [text] or [keyword] instead on [identity_username]]


The elasticsearch version was 5.1.1.

Is this expected for now?

I couldn't see a simple way round this in the code.


Re: JanusGraph 0.1.1 Released

Henry Saputra <henry....@...>
 

Congrats, all!

- Henry

On Tue, May 16, 2017 at 6:56 AM, Ted Wilmes <twi...@...> wrote:
Hello,

We are excited to announce the release of JanusGraph 0.1.1. JanusGraph is an Apache TinkerPop enabled property graph database with support for a variety of storage and indexing backends.

The release artifacts can be found at this location:


The online docs can be found here:


The release notes are available here:


The Central Maven repo is up to date:


Enjoy!
Ted Wilmes

--
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-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: JanusGraph 0.1.1 Released

Austin Sharp <austins...@...>
 

Thanks all for the relatively quick turnaround getting the *-ids table upgrade fix into a release. Much appreciated for those of us with production DBs on Titan!


On Tuesday, May 16, 2017 at 6:56:19 AM UTC-7, Ted Wilmes wrote:
Hello,

We are excited to announce the release of JanusGraph 0.1.1. JanusGraph is an Apache TinkerPop enabled property graph database with support for a variety of storage and indexing backends.

The release artifacts can be found at this location:


The online docs can be found here:


The release notes are available here:


The Central Maven repo is up to date:


Enjoy!
Ted Wilmes


Re: [VOTE] Elasticsearch upgrade

Nigel Brown <ni...@...>
 

I was looking to implement this, but you already did it. 
Great job - thanks.


Re: New TSC member: sjudeng

Jerry He <jerr...@...>
 

Congrats, sjudeng!


Jerry

On Mon, May 15, 2017 at 11:01 AM, Jason Plurad <plu...@...> wrote:
The Technical Steering Committee (TSC) for JanusGraph is pleased to welcome sjudeng as a TSC member on the project (effective May 10). sjudeng has provided major contributions and has demonstrated an on-going commitment to the project in these initial months. Being a TSC member enables assistance with the project management and to guide the direction of the project.

Congratulations to sjudeng and we're looking forward to building up the JanusGraph community with you!

--
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-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


JanusGraph 0.1.1 Released

Ted Wilmes <twi...@...>
 

Hello,

We are excited to announce the release of JanusGraph 0.1.1. JanusGraph is an Apache TinkerPop enabled property graph database with support for a variety of storage and indexing backends.

The release artifacts can be found at this location:


The online docs can be found here:


The release notes are available here:


The Central Maven repo is up to date:


Enjoy!
Ted Wilmes


New TSC member: sjudeng

Jason Plurad <plu...@...>
 

The Technical Steering Committee (TSC) for JanusGraph is pleased to welcome sjudeng as a TSC member on the project (effective May 10). sjudeng has provided major contributions and has demonstrated an on-going commitment to the project in these initial months. Being a TSC member enables assistance with the project management and to guide the direction of the project.

Congratulations to sjudeng and we're looking forward to building up the JanusGraph community with you!


[RESULT][VOTE] JanusGraph 0.1.1 Release

Ted Wilmes <twi...@...>
 

This vote is now closed with a total of 5 +1s, no +0s and no -1s. The results are:

BINDING VOTES:

+1 (4) -- Ted Wilmes, Misha Brukman, Alexander Patrikalakis, P. Taylor Goetz
0   (0)
-1  (0)

NON-BINDING VOTES:

+1 (1) -- Rafael Fernandes
0   (0)
-1  (0)

Thanks for taking the time to test the release and vote everyone.

I'll get the final release steps done later today and add the signatures to the source so that we can announce tomorrow morning.

Thank you very much,
Ted Wilmes


Re: [VOTE] JanusGraph 0.1.1 Release

"P. Taylor Goetz" <ptg...@...>
 

+1 for the release.

I had issues with some of the ES unit/integration tests but I don't see that as a blocker.

-Taylor

On May 11, 2017, at 2:47 PM, P. Taylor Goetz <ptg...@...> wrote:

I’m still reviewing the RC, but a few quick notes:

- We should probably also provide signatures for the source archives (in Apacheland releases are source-only, binary distributions are considered “convenience binaries” and are technically not an official release)
- Do we want to include tar.gz archives as well for platforms that do not provide zip out of the box?

-Taylor


On May 11, 2017, at 11:42 AM, Ted Wilmes <twi...@...> wrote:

Hello,

We are happy to announce that JanusGraph 0.1.1 is ready for release.

The release artifacts can be found at this location:
        
A binary distribution is provided for user convenience:

The GPG key used to sign the release artifacts is available at:

The docs can be found here:

The release tag in Git can be found here:

The release notes are available here:

This [VOTE] will open for the next 72 hours --- closing Sunday (5/14/2017) at 11:00 AM CST.

My vote is +1.

Thank you very much,
Ted Wilmes

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


Re: [VOTE] JanusGraph 0.1.1 Release

Alexander Patrikalakis <amcpatr...@...>
 

+1 for the release
Signatures for all release archives including source and binary.


On Saturday, May 13, 2017 at 6:58:03 AM UTC+9, Ted Wilmes wrote:
Good points, Taylor. I like the idea of including the tar.gz. The source archives are automatically generated/attached by the GitHub release process but we should still be able to attach signatures for them.

Thanks,
Ted

On Thursday, May 11, 2017 at 1:47:17 PM UTC-5, P. Taylor Goetz wrote:
I’m still reviewing the RC, but a few quick notes:

- We should probably also provide signatures for the source archives (in Apacheland releases are source-only, binary distributions are considered “convenience binaries” and are technically not an official release)
- Do we want to include tar.gz archives as well for platforms that do not provide zip out of the box?

-Taylor


On May 11, 2017, at 11:42 AM, Ted Wilmes <t...@...> wrote:

Hello,

We are happy to announce that JanusGraph 0.1.1 is ready for release.

The release artifacts can be found at this location:
        
A binary distribution is provided for user convenience:

The GPG key used to sign the release artifacts is available at:

The docs can be found here:

The release tag in Git can be found here:

The release notes are available here:

This [VOTE] will open for the next 72 hours --- closing Sunday (5/14/2017) at 11:00 AM CST.

My vote is +1.

Thank you very much,
Ted Wilmes

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


Re: [VOTE] JanusGraph 0.1.1 Release

Ted Wilmes <twi...@...>
 

Good points, Taylor. I like the idea of including the tar.gz. The source archives are automatically generated/attached by the GitHub release process but we should still be able to attach signatures for them.

Thanks,
Ted


On Thursday, May 11, 2017 at 1:47:17 PM UTC-5, P. Taylor Goetz wrote:
I’m still reviewing the RC, but a few quick notes:

- We should probably also provide signatures for the source archives (in Apacheland releases are source-only, binary distributions are considered “convenience binaries” and are technically not an official release)
- Do we want to include tar.gz archives as well for platforms that do not provide zip out of the box?

-Taylor


On May 11, 2017, at 11:42 AM, Ted Wilmes <twi...@...> wrote:

Hello,

We are happy to announce that JanusGraph 0.1.1 is ready for release.

The release artifacts can be found at this location:
        
A binary distribution is provided for user convenience:

The GPG key used to sign the release artifacts is available at:

The docs can be found here:

The release tag in Git can be found here:

The release notes are available here:

This [VOTE] will open for the next 72 hours --- closing Sunday (5/14/2017) at 11:00 AM CST.

My vote is +1.

Thank you very much,
Ted Wilmes

--
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-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [VOTE] JanusGraph 0.1.1 Release

Rafael Fernandes <luizr...@...>
 

+1


Re: [VOTE] JanusGraph 0.1.1 Release

"P. Taylor Goetz" <ptg...@...>
 

I’m still reviewing the RC, but a few quick notes:

- We should probably also provide signatures for the source archives (in Apacheland releases are source-only, binary distributions are considered “convenience binaries” and are technically not an official release)
- Do we want to include tar.gz archives as well for platforms that do not provide zip out of the box?

-Taylor


On May 11, 2017, at 11:42 AM, Ted Wilmes <twi...@...> wrote:

Hello,

We are happy to announce that JanusGraph 0.1.1 is ready for release.

The release artifacts can be found at this location:
        
A binary distribution is provided for user convenience:

The GPG key used to sign the release artifacts is available at:

The docs can be found here:

The release tag in Git can be found here:

The release notes are available here:

This [VOTE] will open for the next 72 hours --- closing Sunday (5/14/2017) at 11:00 AM CST.

My vote is +1.

Thank you very much,
Ted Wilmes

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

1341 - 1360 of 1585