Date   

Re: [VOTE] JanusGraph 0.5.0 release

Oleksandr Porunov <alexand...@...>
 

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.


Re: [VOTE] JanusGraph 0.5.0 release

Oleksandr Porunov <alexand...@...>
 

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.


Re: [VOTE] JanusGraph 0.5.0 release

Jan Jansen <faro...@...>
 

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


Re: [VOTE] JanusGraph 0.5.0 release

nicolas...@...
 

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. 

Le mardi 17 mars 2020 11:27:44 UTC+1, Nicolas Trangosi a écrit :
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




Le vendredi 13 mars 2020 21:18:21 UTC+1, Oleksandr Porunov a écrit :
Thank you Ted for the review of the release!
Yes, I also noticed that now jdk is included into elasticsearch.
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.

On Friday, March 13, 2020 at 9:18:15 AM UTC-7, Ted Wilmes wrote:
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

On Thursday, March 12, 2020 at 1:32:36 PM UTC-5, Oleksandr Porunov wrote:
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)

On Wednesday, March 11, 2020 at 10:49:25 PM UTC-7, Oleksandr Porunov wrote:
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


Re: [VOTE] JanusGraph 0.5.0 release

nicolas...@...
 

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




Le vendredi 13 mars 2020 21:18:21 UTC+1, Oleksandr Porunov a écrit :
Thank you Ted for the review of the release!
Yes, I also noticed that now jdk is included into elasticsearch.
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.

On Friday, March 13, 2020 at 9:18:15 AM UTC-7, Ted Wilmes wrote:
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

On Thursday, March 12, 2020 at 1:32:36 PM UTC-5, Oleksandr Porunov wrote:
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)

On Wednesday, March 11, 2020 at 10:49:25 PM UTC-7, Oleksandr Porunov wrote:
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


Re: [VOTE] JanusGraph 0.5.0 release

Oleksandr Porunov <alexand...@...>
 

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.

On Friday, March 13, 2020 at 9:18:15 AM UTC-7, Ted Wilmes wrote:
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

On Thursday, March 12, 2020 at 1:32:36 PM UTC-5, Oleksandr Porunov wrote:
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)

On Wednesday, March 11, 2020 at 10:49:25 PM UTC-7, Oleksandr Porunov wrote:
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


Re: [VOTE] JanusGraph 0.5.0 release

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

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


On Thursday, March 12, 2020 at 1:32:36 PM UTC-5, Oleksandr Porunov wrote:
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)

On Wednesday, March 11, 2020 at 10:49:25 PM UTC-7, Oleksandr Porunov wrote:
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


Re: [VOTE] JanusGraph 0.5.0 release

Oleksandr Porunov <alexand...@...>
 

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)


On Wednesday, March 11, 2020 at 10:49:25 PM UTC-7, Oleksandr Porunov wrote:
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


[VOTE] JanusGraph 0.5.0 release

Oleksandr Porunov <alexand...@...>
 

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


Re: [DISCUSS] JanusGraph 0.5.0 release

Oleksandr Porunov <alexand...@...>
 

Yes, would you be able to include it?

On Wed, Mar 11, 2020 at 3:10 PM 'Jan Jansen' via JanusGraph developers <janusgr...@...> wrote:
Okay.

Should we include the refactoring of hadoop in the notable feature list.



Am Mittwoch, 11. März 2020 22:46:47 UTC+1 schrieb Oleksandr Porunov:
I would like to release 0.5.0 before creating a new branch and bumping it to 0.6.0-SNAPSHOT. Currently I am trying to fix release process which is broken in 0.5.0 release. We didn't shade some dependency correctly, so some of our jars are broken.
I fixed it, but I still experiencing some errors during releasing. I will try to fix those problems asap

On Wednesday, March 11, 2020 at 2:42:00 PM UTC-7, Jan Jansen wrote:
Do you like to create a new branch and bump snapshot version to 0.6.0-SNAPSHOT?

Am Dienstag, 10. März 2020 05:35:07 UTC+1 schrieb Oleksandr Porunov:
v0.5.0 release PR: https://github.com/JanusGraph/janusgraph/pull/2034

On Monday, January 27, 2020 at 3:01:49 AM UTC-8, Jan Jansen wrote:
I would like to get following PR https://github.com/JanusGraph/janusgraph/pull/1940 merged before releasing 0.5.0. This would prevent to breaking changes of janusgraph-hadoop in two releases.

--
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/LhZBlw0_N3o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to janusgr...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/2875ca15-0d8f-4a06-bc2a-dfe6c9bda103%40googlegroups.com.


Re: [DISCUSS] JanusGraph 0.5.0 release

Jan Jansen <faro...@...>
 

Okay.

Should we include the refactoring of hadoop in the notable feature list.



Am Mittwoch, 11. März 2020 22:46:47 UTC+1 schrieb Oleksandr Porunov:

I would like to release 0.5.0 before creating a new branch and bumping it to 0.6.0-SNAPSHOT. Currently I am trying to fix release process which is broken in 0.5.0 release. We didn't shade some dependency correctly, so some of our jars are broken.
I fixed it, but I still experiencing some errors during releasing. I will try to fix those problems asap

On Wednesday, March 11, 2020 at 2:42:00 PM UTC-7, Jan Jansen wrote:
Do you like to create a new branch and bump snapshot version to 0.6.0-SNAPSHOT?

Am Dienstag, 10. März 2020 05:35:07 UTC+1 schrieb Oleksandr Porunov:
v0.5.0 release PR: https://github.com/JanusGraph/janusgraph/pull/2034

On Monday, January 27, 2020 at 3:01:49 AM UTC-8, Jan Jansen wrote:
I would like to get following PR https://github.com/JanusGraph/janusgraph/pull/1940 merged before releasing 0.5.0. This would prevent to breaking changes of janusgraph-hadoop in two releases.


Re: [DISCUSS] JanusGraph 0.5.0 release

Oleksandr Porunov <alexand...@...>
 

I would like to release 0.5.0 before creating a new branch and bumping it to 0.6.0-SNAPSHOT. Currently I am trying to fix release process which is broken in 0.5.0 release. We didn't shade some dependency correctly, so some of our jars are broken.
I fixed it, but I still experiencing some errors during releasing. I will try to fix those problems asap

On Wednesday, March 11, 2020 at 2:42:00 PM UTC-7, Jan Jansen wrote:
Do you like to create a new branch and bump snapshot version to 0.6.0-SNAPSHOT?

Am Dienstag, 10. März 2020 05:35:07 UTC+1 schrieb Oleksandr Porunov:
v0.5.0 release PR: https://github.com/JanusGraph/janusgraph/pull/2034

On Monday, January 27, 2020 at 3:01:49 AM UTC-8, Jan Jansen wrote:
I would like to get following PR https://github.com/JanusGraph/janusgraph/pull/1940 merged before releasing 0.5.0. This would prevent to breaking changes of janusgraph-hadoop in two releases.


Re: [DISCUSS] JanusGraph 0.5.0 release

Jan Jansen <faro...@...>
 

Do you like to create a new branch and bump snapshot version to 0.6.0-SNAPSHOT?

Am Dienstag, 10. März 2020 05:35:07 UTC+1 schrieb Oleksandr Porunov:

v0.5.0 release PR: https://github.com/JanusGraph/janusgraph/pull/2034

On Monday, January 27, 2020 at 3:01:49 AM UTC-8, Jan Jansen wrote:
I would like to get following PR https://github.com/JanusGraph/janusgraph/pull/1940 merged before releasing 0.5.0. This would prevent to breaking changes of janusgraph-hadoop in two releases.


Re: [DISCUSS] JanusGraph 0.5.0 release

Oleksandr Porunov <alexand...@...>
 

v0.5.0 release PR: https://github.com/JanusGraph/janusgraph/pull/2034


On Monday, January 27, 2020 at 3:01:49 AM UTC-8, Jan Jansen wrote:
I would like to get following PR https://github.com/JanusGraph/janusgraph/pull/1940 merged before releasing 0.5.0. This would prevent to breaking changes of janusgraph-hadoop in two releases.


Re: Interests in a transactional scale-out graph store backend for JanusGraph?

Dmitry Kovalev <dk.g...@...>
 

Hi Gene,

just curious - any news on this project? Any github links to share?

Thank you,
Dmitry


On Wednesday, 28 August 2019 17:21:14 UTC+1, Gene Z wrote:
Hi Oleksandr,

I can share some high-level information here.

The transactional graph store backend consists two main parts:

The replication is through LogStores, which the LogPlayers play to the backend servers within the same DCs.


-Gene


On Wednesday, August 28, 2019 at 1:49:11 AM UTC-7, Oleksandr Porunov wrote:
Hi Gene,

It is always interesting to see new store backends.
It would be interesting to see the main concepts behind this backend.
Personally I am interested in transactions management mechanism. Is it works something like InnoDB transactions in MySQL? Is the row with the data is locked during the "update" / "read for update"? Is the data is locked in all replicas? If no, how do you choose what replicas to lock? etc.

Please, share some details when this backend is open source.

Best regards,
Oleksandr

On Tuesday, August 27, 2019 at 8:59:56 PM UTC+3, Gene Z wrote:
Hi JanusGraph developers,

We at eBay have been developing a transactional scale-out graph store backend specifically for JanusGraph to address data inconsistency problems with non-transactional backends.
The system consists of various components written in C++, at different maturity levels. But overall system works functionally. We intend to move the further development to the open source with Apache 2.0 license and try to see the interests and potential contributions from the open source community.

If you are interested, and can contribute to develop and or use/test the system, please let me know, and I can share more details, in the meantime we are going through the open source process.

Best regards,
Gene


Re: [DISCUSS] Removal of janusgraph-codepipelines-ci and coverity scans

Oleksandr Porunov <alexand...@...>
 

+1 for removing those tools. Currently they don't add any benefit to JanusGraph but add only some inconvenience (i.e. they are distracting)


On Monday, March 2, 2020 at 12:24:44 PM UTC-8, Jan Jansen wrote:
Hello

The JanusGraph repo have two tools which aren't used for a long time. I'm proposing to delete these tools.
Both tools could be broken and also the main repo should be clean as possible.

* janusgraph-codepipelines-ci a tool to run JanusGraph tests inside aws. We are currently in state where we can ran the most tests inside Travis.
* coverity some static analysis which also done by Codacy

What do you think?

Greetings,
Jan



Re: High Severity Bug related meta properties - When trying to load graph , meta properties are not being set on vertex properties , bug found , it required fix for this blocker

Florian Hockmann <f...@...>
 

The developer list is only meant to discuss development of JanusGraph and not to report a bug or suggest a feature. You already created an issue for this in our issue tracker: https://github.com/JanusGraph/janusgraph/issues/1996 so you don't have to repeat this here again.

To copy what I wrote on Gitter where you also tried to bump this:

JanusGraph is a community driven project so if meta properties in a custom vertex program are an important feature for you, then you can contribute this yourself. Otherwise you'll have to wait until someone else with knowledge about this part of the code base wants to work on this. But that won't happen any faster by spamming the issue on every possible channel and by tagging specific people. This is actually considered kind of rude and therefore won't motivate people to help you.

Am Dienstag, 3. März 2020 13:22:21 UTC+1 schrieb Ramesh Babu Y:


High Severity Bug related meta properties - When trying to load graph , meta properties are not being set on vertex properties , bug found , it required fix for this blocker

Ramesh Babu Y <ramesh...@...>
 


[DISCUSS] Removal of janusgraph-codepipelines-ci and coverity scans

Jan Jansen <faro...@...>
 

Hello

The JanusGraph repo have two tools which aren't used for a long time. I'm proposing to delete these tools.
Both tools could be broken and also the main repo should be clean as possible.

* janusgraph-codepipelines-ci a tool to run JanusGraph tests inside aws. We are currently in state where we can ran the most tests inside Travis.
* coverity some static analysis which also done by Codacy

What do you think?

Greetings,
Jan



Re: [DISCUSS] Revamp JanusGraph Management

Jan Jansen <faro...@...>
 

An HTTP API would have the benefit of making the schema management available to users of the Gremlin server without the mentioned problems for making it accessible via Gremlin. As it would just expose the underlying Java API (current or a new one), it would be 

nice if the web service would be optional if JG is used embedded.


+1

One of my major concerns is to make JanusGraph more modular.

281 - 300 of 1601