by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 30 2019 15:47
    MOZGIII starred elastic-rs/elastic
  • Jan 30 2019 03:32
    KodrAus commented #277
  • Jan 28 2019 00:44
    KodrAus edited #319
  • Jan 28 2019 00:44
    KodrAus edited #319
  • Jan 27 2019 10:23
    KodrAus closed #317
  • Jan 27 2019 10:23
    KodrAus commented #317
  • Jan 27 2019 10:22

    KodrAus on tidy-ups

    (compare)

  • Jan 27 2019 10:22

    KodrAus on master

    Some modernization (#320) * ru… (compare)

  • Jan 27 2019 10:22
    KodrAus closed #320
  • Jan 27 2019 10:22
    KodrAus closed #316
  • Jan 27 2019 09:59
    KodrAus synchronize #320
  • Jan 27 2019 09:59

    KodrAus on tidy-ups

    run fmt (compare)

  • Jan 27 2019 09:59
    KodrAus synchronize #320
  • Jan 27 2019 09:59

    KodrAus on tidy-ups

    fix up integration tests (compare)

  • Jan 27 2019 05:14
    KodrAus synchronize #320
  • Jan 27 2019 05:14

    KodrAus on tidy-ups

    update examples fix up doc tests (compare)

  • Jan 27 2019 02:03
    KodrAus edited #320
  • Jan 26 2019 23:40
    KodrAus commented #320
  • Jan 26 2019 11:42
    KodrAus synchronize #320
  • Jan 26 2019 11:42

    KodrAus on tidy-ups

    update dependencies (compare)

Ashley Mannix
@KodrAus
Hi @stephanbuys :wave: I thought I'd set up a gitter chat for elastic so we can chat about things that might not fit nicely into a GitHub issue
Ashley Mannix
@KodrAus
I'm tweaking things around a bit so we can work on both breaking and non-breaking changes together. I've got a vNext branch we can merge breaking changes into, and non-breaking changes can go straight into master and released on crates.io right away. So that way master is always 'current'
I'll update CI to build docs off vNext
Ashley Mannix
@KodrAus
Ok, I've got all the branches sorted out and am making some progress on load balancing
Stephan Buys
@stephanbuys
nice surprise (logging into gitter for the first time in a while :-) )
Arnaud Esteve
@aesteve
Hello folks, not sure if this channel is still active or not, but I'll give it a try. First of all, thanks a lot for your work.
I tried to create a very very basic example using the "high-level" stuff like macros, etc. but it's just not working
even though my struct has the #[elastic(index = "stuff")] macro, I can't use it in Stuff::static_index() "function or associated item not found
same goes for client.document::<Stuff>() this simply does not exist
I've read the doc and examples carefully (I hope so) and I'm really really struggling with this, I've added #[macro_use] extern crate elastic_derive; etc.
what should I do ? that sounds like a very very good library, the macro use is really cool, but I can't get anythiong working
Ashley Mannix
@KodrAus
Hi @aesteve :wave: Sorry to hear you're running into trouble. I think the problem might be that I've just merged a lot of refactoring onto the master branch that hasn't made its way onto crates.io. So they're quite different libraries. I'll fix that up by pushing out a pre-release version so what's on crates.io is closer to what's on GitHub
Arnaud Esteve
@aesteve
oh cool !
just let me know then
Ashley Mannix
@KodrAus
It's quite late here though so I'll sort that out in the morning :)
Arnaud Esteve
@aesteve
no worries :)
skvithalani
@skvithalani

Hello all, I am quite new to ELK stack and we need to recommend a free license to our client. our basic doubt is why x-pack in 6.3 is basic license and not oss. What are catches we should be aware of in terms of x-pack being basic license when they say it is free.

We have formed the understanding that x-pack will offer some of the features under basic(free) license and some under paid (gold or platinum) license. The part of x-pack that comes under basic license sit in the same github repo as oss elasticsearch but the x-pack license is basic and rest other code is oss.