Show HN: GUI for Data Modeling with Elasticsearch • Hacker News Board

Re: Show HN: GUI for Data Modeling with Elasticsearch

#11

Post by sidi » Thu, Dec 01, 2016, 9:48 PM UTC

serguzest wrote: post #4

I am trying to connect ES 2.3.3 Nothing happens, in chrome console I see those errors : XMLHttpRequest cannot load http://localhost:9200/myindex/_settings . Response to preflight request doesn't pass access control check: A wildcard '*' cannot be used in the 'Access-Control-Allow-Origin' header when the credentials flag is true. Origin ' http://opensource.appbase.io' is therefore not allowed access. The credentials m…

@serguzest: Updated the instructions for using as an Elasticsearch plugin - https://github.com/appbaseio/gem/blob/dev/README.md#install-.... If you still see the error, feel free to file an issue.

Re: Show HN: GUI for Data Modeling with Elasticsearch

#12

Post by NikolaeVarius » Thu, Dec 01, 2016, 9:50 PM UTC

sidi wrote: post #7

NikolaeVarius wrote: post #5

Earlier quoted context omitted.

DAMNIT. Been working on my own spin on this sort of GUI internally for my company. Are you guys actively taking pull requests? I would much rather contribute to a more finished application

It's in active development. We would love PRs that are aligned, what areas are you looking to contribute in?

Going through the code right now and seeing what you guys have/need.

Re: Show HN: GUI for Data Modeling with Elasticsearch

#13

Post by IndianAstronaut » Fri, Dec 02, 2016, 6:18 AM UTC

sidi wrote: post #2

One of the contributers here: GEM is at the first step towards true data modeling where it makes the mappings process very accessible. For someone coming from a SQL background, mappings in Elasticsearch are interesting because of it's nature of being both a search engine and a data store suited for aggregations. Would love it to eventually have some intelligence and heuristics built in, like recommending what data ty…

Very interesting. Have you tested it fully on a wide array of geolocation data? Such as what are the mappings for a variety of cities and towns, where some may fit a string definition or geolocation, such as "Pleasant".

I have used Solr quite a bit, not much Elasticsearch, but I am assuming the text tokenizers/analyzers aren't as complex in the schemas as Solr is, where you have a wide array of different text parsers.