sidi

My biggest gripe with the 6.0.0 GA is the removal of multiple mapping types per index. This creates a significant breaking change that will hurt the community tools adoption to 6.0. Their initial plan was to deprecate it and only remove it v7 onwards, which imho would've been a better balance.

Not a lawyer, to be on the safe side - you would want to avoid a scenario where you are getting paid or do anything that may be treated as skilled labor while on a B1/B2 visa. Breaking this may be grounds for revoking your visa status.

You can be compensated for your travel, meal, lodging expenses from a US entity, and you can take meetings, close deals, fundraise, and perform other business activities.

Update: You may have personal funds in your country that you would use for covering your expenses and that should be okay. Any ambiguity with such costs being a payment (you mentioned it a subsidiary) for services rendered should be avoided.

Not true. Oracle's P/E is 22, Apple's is 18, MSFT's is 27. Oracle is doing just fine.

I am not sure if I like this change, more at https://help.medium.com/hc/en-us/articles/115011350967-Claps. In HN analogy, it's like saying you can upvote a post multiple times (up to a max of 50 times). How do you prevent gaming the system in this scenario?

We first did a Show HN ~1.5 years ago; this is a super major overhaul with active development since and close to 100 issue fixes.

Direct link to try it out - https://opensource.appbase.io/dejavu/.

* The biggest change today is the ability to import data into Elasticsearch directly via JSON and CSV files. Their is a guided process for setting the mappings correctly.

* Filtered views and query views.

* Ability to export filtered data as JSON / CSV, apparently other web UIs don't support this.

* There is also a docker image option to run it as Elasticsearch removed website plugins starting v5.0.

We originally wrote it in React v0.14.0 and have made it compatible with the React v15.6. There is an ongoing refactoring effort to translate all the code to use ES6 idioms.

Would like to hear what improvements can be made, I am not perfectly happy with how we are supporting mappings in the import process.

They are similar ideas on the surface, key differences are that we use Elasticsearch as the underlying distributed search engine, InstantSearch is based on Algolia.

Reactive Search also supports more components at this point, most prominent one being maps. We released an entire library https://opensource.appbase.io/reactivemaps dedicated to that earlier and all those are available with ReactiveSearch as well.

The part that I really like about ReactiveSearch is its neat composing of components to form complex search UIs, this abstracts out the need for writing Elasticsearch DSL queries to a large extent.

Sorry about that, this should be fixed now.

You might want to check https://github.com/tomchentw/react-google-maps.

We build on top of it to add the querying functionality and additional components (everything that is not a map).

Reactive Maps is a data components library, the UI components are data aware and can be composed together to create complex filter rich UIs.

While the library is geared towards building maps, the components can be used for generic (components include data aware Lists, Dropdowns, Range Sliders, Button Groups, Searchboxes, Calendars, Feeds, GeoDistance Search and sliders, Maps) UIs.

Some examples of such UIs built with the library are here - https://opensource.appbase.io/reactivemaps/#meetup.

Aim to make your side projects popular: write a blog post, do a show HN, launch on PH. Pick a popularity metric and then nail it.

It would be interesting to hear what are the alternatives now to what they were trying to do with [flocker](https://clusterhq.com/flocker/introduction/).

The post seems to make the point other alternatives came up that removed their competitive advantage. Anyone here either using flocker or the other alternatives?

@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.

While this thread is still active, I would like to share more context around the project:

GEM is built as an auxiliary app to go along with mirage[0] and dejavu[1]. Together, the three can be used to model data, perform CRUD operations and compose queries.

[0]: https://github.com/appbaseio/mirage

[1]: https://github.com/appbaseio/dejavu

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

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 types to choose, data normalization patterns.

I fail to understand this criticism. React Components expose a class hierarchy which can be namespaced well by their designers (if Antd isn't already doing this). Extending / theming with your specific CSS pre-processor is then pretty straightforward.

Google link to read the full article: https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&c...

I believe it's 5000 reqs/hr with an access token.

This is a great idea, kudos! You should consider extending it to *nix systems.

Also like someone here mentioned, it might be good to extend the Fortune 500 with a community contributed list of companies.

I wonder if there are any interesting hacks around stars: like monitoring repositories for major releases, discovering similar projects.

And may be there could be some neat ones if we knew the social constructs associated with them.

I love Unknown Horizons as one of the rare desktop games that's both open-source and built with Python.

On revisiting my past contributions to it some years ago, realized it could use more publicity. Kudos to the team for maintaining it all these years.

Direct github link: https://github.com/unknown-horizons/unknown-horizons

Also, mirage goes well with https://github.com/appbaseio/dejavu for performing CRUD operations on an Elasticsearch index.

This is our support roadmap - https://github.com/appbaseio/mirage#3-roadmap.

We welcome contributions for more queries.

Elasticsearch's plugin ecosystem has historically been fragmented. That's why we make the plugin available in multiple ways (hosted app, chrome extension and site plugin).

Links:

[1] Hosted app - http://appbaseio.github.io/mirage/

[2] Chrome extension - https://chrome.google.com/webstore/detail/mirage/dcnlpfmnpog...

[3] Site Plugin for Elasticsearch v2.x - plugin install appbaseio/mirage

Sense is JSON aware (and autocomplete is nice) but it still expects you to write the Elasticsearch DSL.

Mirage provides an alternative interface (GUI based) to compose the Elasticsearch queries that it transpiles on the fly to the Elasticsearch JSON syntax (and you're free to work with the latter as well).

Hey HN folks,

Elasticsearch has one of the most powerful query DSLs with support for 100+ search APIs ranging from full-text search to geo queries to range filters. At the same time, there is a very high learning curve associated with using Elasticsearch's JSON API.

Our goal with Mirage is to simplify the Elasticsearch APIs by providing GUI blocks for queries. It should also be an ideal resource to learn the ES query DSL as it transforms queries on-the-fly and comes with an in-app documentation browser.

Our current coverage of the DSL and future roadmap - https://github.com/appbaseio/mirage#3-roadmap.

Yes

On first look, it looks great. Wish there were an easier to try it out. Would love to help with that.

Value creation is by far the pre-dominant variable when one thinks about compensation. Arguably, there is more value creation in the process of programming (infinite distribution) than there is in let's say plumbing or some of the other analogies you make here.

The more democratized a field is and the more systematic efficiencies there are to be gained, the more easy it will be to both create and capture value and hence, resulting in a more even playing field for expected compensations. This has historically been true for entrepreneurship, modern-day programming is also a good example of this effect.

As other comments point out, there are significant benefits to having a streaming endpoint over a polling logic. It conserves resources, provides a more elegant representation with an events based interface to act on incoming data.

A latent benefit of Heartbeat (which we will start emphasizing soon) is an ability to filter the incoming stream of events by the JSON data properties, so one can build nice IFTTT style code using any REST based APIs as sources. We are leaning towards creating a monthly and a longer-term pricing plan, but if your use-case is casual, then it will always be free. We are able support the current load of requests with a single worker process.