Re: Geo Data
Robert Dale <rob...@...>
If it's an index query, it should use the index backend. If it's mid-traversal, it will likely use a geo predicate which uses spatial4j [1]. ES, solr use lucene. Lucene also uses spatial4j. So I think in the end everything uses spatial4j. And they all also use JTS [2] to some degree.
Robert Dale On Wed, Jun 7, 2017 at 1:44 AM, JZ <zamb...@...> wrote:
|
||
|
||
Re: Who is using JanusGraph in production?
Liu-Cheng Xu <xuliuc...@...>
Awesome! Could you also share the links here when ready? Tunay Gür <tuna...@...>于2017年6月7日周三 上午6:47写道:
-- Liu-Cheng Xu |
||
|
||
Re: Character case behaviour different with or without indices
ni...@...
Ok, thanks. That is good to know. |
||
|
||
Re: Character case behaviour different with or without indices
tpr...@...
If you want to use both, you have to use TEXTSTRING mapping.
|
||
|
||
Re: Character case behaviour different with or without indices
ni...@...
Great. I was using STRING and TEXT indices and janus was only finding the TEXT one. I stopped using the TEXT index and it started to behave as expected. I had assumed that janus would use the right index based on the query (textRegex vs textContainsRegex). Thanks for your help. |
||
|
||
Geo Data
JZ <zamb...@...>
(1) Was looking at the GEO facilities, does someone know what algorithm or approach is used by the implementation for GEO location calculations? |
||
|
||
Re: Character case behaviour different with or without indices
tpr...@...
Are you using DEFAULT mapping or no Mapping ? If so, DEFAULT mapping or no mapping use TEXT mapping which are bind to Text ES datatype (https://www.elastic.co/guide/en/elasticsearch/reference/current/text.html) which are lowercased by default. So, if you use STRING mapping which is bind to Keyword ES datatype which are untouched by default, it should work. Le mardi 6 juin 2017 23:24:46 UTC+2, Nigel Brown a écrit :
Elasticsearch 5.1.1 |
||
|
||
Re: Who is using JanusGraph in production?
Tunay Gür <tuna...@...>
We are (uber) using JG in production at the moment. We're recently started to contribute some of our code back and it's in plan to publish our learnings, benchmarks etc as series of blog posts. On Monday, June 5, 2017 at 11:53:37 AM UTC-7, Misha Brukman wrote:
|
||
|
||
How to list properties from gremlin console
Gene Fojtik <genef...@...>
Is there a way to list the current graph properties from the gremlin console? Looking for the properties set in the *.properties file that have been sourced on start-up. -gene |
||
|
||
Re: Character case behaviour different with or without indices
Nigel Brown <ni...@...>
Elasticsearch 5.1.1
|
||
|
||
Re: Character case behaviour different with or without indices
tpr...@...
which indexing backend do you use ? Le lundi 5 juin 2017 18:53:40 UTC+2, Nigel Brown a écrit :
|
||
|
||
Indexes stuck in INSTALLED status
Brandon Dean <engr...@...>
I've been struggling with my indexes getting stuck in the INSTALLED status with no apparent way to get them out of that status. After much frustration, I started with a completely fresh install of JanusGraph 0.1.1, left the configuration as is, and then followed the steps from the documentation exactly to create a new composite index. I was able to successfully create my index and it moved into the REGISTERED status and then the ENABLED status after issuing a REINDEX command. 1490727 [gremlin-server-session-1] INFO org.janusgraph.graphdb.database.management.GraphIndexStatusWatchemposite do not currently have status REGISTERED: name=ENABLED I then attempted to follow the documentation to delete this same index using the following steps: gremlin> :remote connect tinkerpop.server /opt/vdp/janus/conf/remote.yaml session gremlin> :remote console gremlin> m = graph.openManagement() gremlin> i = m.getGraphIndex('byNameComposite') gremlin> m.updateIndex(i, SchemaAction.DISABLE_INDEX).get() gremlin> m.commit() Rather than moving to a DISABLED state though, my index is now back in the INSTALLED state and I am unable to move it to REGISTERED or DISABLED. I've tried issuing additional commands to DISABLE or even REGISTER the index but they all time out and the status never changes from INSTALLED. gremlin> m = graph.openManagement() gremlin> i = m.getGraphIndex('byNameComposite') gremlin> i.getIndexStatus(m.getPropertyKey('name')) ==>INSTALLED gremlin> m.rollback() gremlin> m.updateIndex(i, SchemaAction.REMOVE_INDEX).get() Update action [REMOVE_INDEX] cannot be invoked for index with status [INSTALLED] I'm currently the only user on this server. I've performed rollbacks just to be certain and insured that there are no other open instances. Anytime I issue an awaitGraphIndexStatus it times out and the status never changes. What's the proper way to get this index to move out of the INSTALLED status? Alternatively, what might be blocking that from occuring if it is supposed to happen automatically? gremlin> graph.getOpenTransactions() ==>standardjanusgraphtx[0x18489ed6] gremlin> graph.tx().rollback() ==>null gremlin> graph.getOpenTransactions() ==>standardjanusgraphtx[0x18489ed6] gremlin> graph.openManagement().getOpenInstances() ==>0a7f01141301102-dcwidphiat002-edc-nam-gm-com1(current) gremlin> graph.openManagement().awaitGraphIndexStatus(graph, 'byNameComposite').call() Script evaluation exceeded the configured 'scriptEvaluationTimeout' threshold of 30000 ms or evaluation wa request [graph.openManagement().awaitGraphIndexStatus(graph, 'byNameComposite').call()]: sleep interrupte Any help for the new guy (me) would be very much appreciated! |
||
|
||
Re: Odd behavior with elasticsearch and metapropeties
Adam Holley <holl...@...>
I know meta-properties only support single value. My question was, should it return an error when you have a property that is defined as cardinality SET or LIST and you're trying to use it in a meta-property. Additionally, since meta-properties are not indexed, should it return an error if you're trying to use a property that you've indexed? |
||
|
||
Re: Odd behavior with elasticsearch and metapropeties
Robert Dale <rob...@...>
Meta-properties only support single value. http://tinkerpop.apache.org/docs/current/reference/#vertex-properties Robert Dale On Tue, Jun 6, 2017 at 12:53 AM, Adam Holley <holl...@...> wrote:
|
||
|
||
Re: Odd behavior with elasticsearch and metapropeties
david.c...@...
Hi, Your ES does not allowed groovy script. So you have to set "script.engine.groovy.inline.update" to "true" in the yaml of the ES conf. David |
||
|
||
Odd behavior with elasticsearch and metapropeties
Adam Holley <holl...@...>
Here's the setup. I have 4 property keys, all part of a Mixed Index. - name_string, Cardinality.SINGLE, Mapping.STRING.asParameter - meta_name_string, Cardinality.SINGLE, Mapping.STRING.asParameter - name_list, Cardinality.LIST, Mapping.STRING.asParameter - meta_name_list, Cardinality.LIST, Mapping.STRING.asParameter I created a vertex with a name_string and name_list property. Then added some meta properties using meta_name_string, and meta_name_list. The first time I tried to commit, I received the following error: [0]: index [janusgraph], type [basicIndex], id [388], message [ElasticsearchIllegalArgumentException[failed to execute script]; nested: ScriptException[dyoovy] disabled]; ] I enabled script execution and was able to commit. While the metaproperties were not indexed, I did see some additional entries in the name_list when querying the index directly. e.g.: From gremlin:
From elasticsearch:
This may be a bad pattern, but should have I expected adding metaproperties with properties defined in the index to fail since they are not indexed? Additionally, should trying to use a property with Cardinality != SINGLE, fail for metaproperties? The additional items in the name_list in the index are not really a problem since I get the properties from gremlin, but it seems like it might be a problem. Or am I doing something wrong when creating the index? Thanks. Adam. |
||
|
||
Re: Who is using JanusGraph in production?
Misha Brukman <mbru...@...>
Great point! I welcome case studies and in-depth descriptions, but those take a significant effort to write as well as get approved by appropriate PR/Legal/etc. departments, so while I am always advocating for these, it's not always going to be possible. In the meantime, here's one from CELUM (will be added shortly to the website): https://www.celum.com/en/graph-driven-and-reactive-architecture and I hope we'll be adding more of these in the future. On Mon, Jun 5, 2017 at 2:46 PM, Michael Markieta <mark...@...> wrote:
|
||
|
||
Re: Who is using JanusGraph in production?
Michael Markieta <mark...@...>
It would be great if the current user list also said a little bit about how they use it. It's impossible to tell how FiNQ and Seeq are using JanusGraph. We would benefit from having case study like material for others to look at (in due time). On Saturday, 27 May 2017 08:13:17 UTC-4, Jimmy wrote:
|
||
|
||
Re: Character case behaviour different with or without indices
ni...@...
I should point out that I am using a build from master 0.2.0. |
||
|
||
Re: Is textRegex using search backends?
ni...@...
I should point out that I am using a build from master 0.2.0. |
||
|