Christopher Smith created TINKERPOP-2507:
Summary: TinkerGraph erroneously assumes IDs must be homogeneous
Key: TINKERPOP-2507
URL: https://issues.apache.org/jira/browse/TINKERPOP-2507
Project:
VOTE +1
Cheers,Kelvin
On Monday, January 18, 2021, 05:29:43 PM CST, Stephen Mallette
wrote:
Hello,
We are happy to announce that TinkerPop 3.4.10 is ready for release.
The release artifacts can be found at this location:
https://dist.apache.org/repos/dist/dev/tinkerpop/3.4.10
vote +1
On Mon, Jan 18, 2021 at 3:29 PM Stephen Mallette
wrote:
> Hello,
>
> We are happy to announce that TinkerPop 3.4.10 is ready for release.
>
> The release artifacts can be found at this location:
> https://dist.apache.org/repos/dist/dev/tinkerpop/3.4.10/
>
> The source distrib
Is there a way to do this so that createDefaultYamlConstructor() is not
public? Perhaps you could make it protected scope and then create a
JanusGraphServerSettings to extend it so you could access it that way? I
guess I'm just thinking that Settings shouldn't publicly expose yaml
related details l
Ebrahim created TINKERPOP-2506:
--
Summary: Expose client WebSocket connection status
Key: TINKERPOP-2506
URL: https://issues.apache.org/jira/browse/TINKERPOP-2506
Project: TinkerPop
Issue Type: I