[VOTE] JanusGraph 0.5.0 release

[Oleksandr Porunov]

Hello,

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

The release artifacts can be found at this location:
        https://github.com/JanusGraph/janusgraph/releases/tag/v0.5.0

A binary distribution is provided for user convenience:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.5.0/janusgraph-0.5.0.zip

The GPG key used to sign the release artifacts is available at:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.5.0/KEYS

The docs can be found here:
        https://github.com/JanusGraph/janusgraph/releases/download/v0.5.0/janusgraph-0.5.0-doc.zip

The release tag in Git can be found here:
        https://github.com/JanusGraph/janusgraph/tree/v0.5.0

The release notes are available here:
        https://github.com/JanusGraph/janusgraph/blob/master/docs/changelog.md#version-050-release-date-march-10-2020

This [VOTE] will open for the next 3 days --- closing Saturday, March 15, 2020 at 06:00 AM GMT.
All are welcome to review and vote on the release, but only votes from TSC members are binding.
My vote is +1.

Thank you,
Oleksandr Porunov

[Oleksandr Porunov]

I want to say that the release is targeting the latest commit: https://github.com/JanusGraph/janusgraph/commit/c01bfea2ce602696163aa50fde9be1cdeea13fc1

The release has been tested with following steps:

1) All TinkerPop tests passed using `mvn clean install -Dtest.skip.tp=false -DskipTests=true`
2) TravisCI build passed: https://travis-ci.org/github/JanusGraph/janusgraph/builds/661377366
3) Custom full build passed also: https://travis-ci.org/github/porunov/janusgraph/builds/661374484
4) Custom integrationTests passed for the release (ScyllaDB + ElasticSearch)

[Ted Wilmes]

Thanks for leading this release Oleksandr!

I downloaded 0.5.0 and noticed the zip is quite large. It looks like there is a jdk that got bundled under Elasticsearch:

20M     janusgraph-0.5.0/elasticsearch/bin

273M    janusgraph-0.5.0/elasticsearch/jdk

153M    janusgraph-0.5.0/elasticsearch/modules

40K     janusgraph-0.5.0/elasticsearch/config

4.0K    janusgraph-0.5.0/elasticsearch/plugins

35M     janusgraph-0.5.0/elasticsearch/lib

479M    janusgraph-0.5.0/elasticsearch

Here's the 0.4.1 Elasticsearch directory:

260K    janusgraph-0.4.1-hadoop2/elasticsearch/bin

8.5M    janusgraph-0.4.1-hadoop2/elasticsearch/modules

20K     janusgraph-0.4.1-hadoop2/elasticsearch/config

4.0K    janusgraph-0.4.1-hadoop2/elasticsearch/plugins

22M     janusgraph-0.4.1-hadoop2/elasticsearch/lib

31M     janusgraph-0.4.1-hadoop2/elasticsearch

Thanks,

Ted

[Oleksandr Porunov]

Thank you Ted for the review of the release!

Yes, I also noticed that now jdk is included into elasticsearch.

This change was made in the next commit: https://github.com/JanusGraph/janusgraph/commit/c16f5c28c859f1ab209e344a1a83ee4f07038c8f

Before that commit we were executing assembly tests against ElasticSearch 6.2.4

After that commit we changed the behavior and now we are executing assembly tests against ElasticSearch {elasticsearch.version} (which is 7.6.1 right now).

ES 7.x depends on java 13, so I assume that is why they included openjdk 13 into the elasticsearch 7.x releases.

I am not sure if we can exclude jdk 13 from the distribution now. I think it should be there now to work with newer ES releases. But this dependency is only for distribution. It isn't populated into maven, so I guess it is OK.

[nicolas....@dcbrain.com]

Hi,

I have tested the release using cassandra 3.0.17 and elasticsearch 6.8.6.

I have been able to use a graph loaded with janusGraph 0.4.1. 

I have also created a new graph with about 800 000 vertices and same number of edges.

I have some deprecation messages that appears when I create the elastic search index:

17 Mar 2020 10:41:37,961 26392 [gremlin-server-exec-3] WARN  org.elasticsearch.client.RestClient  - request [PUT http://localhost:9200/dcbrain_devicesearchbyname] returned 1 warnings: [299 Elasticsearch-6.8.6-3d9f765 "the default number of shards will change from [5] to [1] in 7.0.0; if you wish to continue using the default of [5] shards, you must manage this on the create index request or with an index template"]
17 Mar 2020 10:41:38,238 26669 [gremlin-server-exec-3] WARN  org.elasticsearch.client.RestClient  - request [PUT http://localhost:9200/dcbrain_devicesearchbyname/_mapping/deviceSearchByName] returned 1 warnings: [299 Elasticsearch-6.8.6-3d9f765 "[types removal] Specifying types in put mapping requests is deprecated. To be compatible with 7.0, the mapping definition should not be nested under the type name, and the parameter include_type_name must be provided and set to false."]

I have not found how to prevent such warnings.

My vote is +1

Kind regards,

Nicolas

[nicolas....@dcbrain.com]

Hi,

I found how to fix the warning "the default number of shards will change from [5] to [1] in 7.0.0" with the option index.search.elasticsearch.create.ext.number_of_shards documentated at https://docs.janusgraph.org/master/index-backend/elasticsearch/.

As this option is not documentated at https://docs.janusgraph.org/master/basics/configuration-reference/, I will try do a merge request to fix it, this week. 

[Jan Jansen]

We could think of adding a smaller release bundle without janusgraph.sh, cassandra and elasticsearch.

For the current release, we could try to run elasticsearch with default jdk. It shouldn't be any problem.
This will postpone the release.

I'm currently working on testing hadoop changes.

Greetings,

Jan

[Oleksandr Porunov]

Hi Nicolas. This isn't a release specific warning but ES specific. You may find the same warning with JanusGraph 0.3.x, 0.4.x versions.

[Oleksandr Porunov]

Hi Jan,

I think that it isn't a big problem that current release is 2 times bigger than past releases. Of course we can try to ship also truncated releases but it looks more like a new feature. We actually can add a truncated opinion to all current JanusGraph releases but I think we need to discuss it in a separate thread. I don't think we should postpone the release because of its size (0.5 GB) but if you think that it is a problem and we should also add a truncated option to this release, I am OK with it.

[Jan Jansen]

I am OK with it. I would prefer to work on truncated short after this release and release 0.5.1 also as truncated release.

If opened two PRs for the docker images which are required for releasing docker images for 0.5.

I think tomorrow will able give a vote. I have to check the hadoop part.

[Oleksandr Porunov]

Thank you Jan.
Yes, I think we can release 0.5.1 as a truncated version short after 0.5.0 release.

[Jan Jansen]

Vote +1

[Ted Wilmes]

Vote +1

--
You received this message because you are subscribed to a topic in the Google Groups "JanusGraph developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/janusgraph-dev/ejs-BAbu7wM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to janusgraph-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/6d1957f4-1241-4565-94df-9fa56002f105%40googlegroups.com.