Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 15 15:45
    niemyjski synchronize #452
  • Nov 15 15:45

    niemyjski on elastic7

    Fixed reindex mapping issues on… (compare)

  • Nov 15 03:05
    foresightyj closed #467
  • Nov 15 03:05
    foresightyj commented #467
  • Nov 15 03:03
    foresightyj edited #467
  • Nov 15 03:02
    foresightyj opened #467
  • Nov 14 14:41
    niemyjski synchronize #452
  • Nov 14 14:41

    niemyjski on elastic7

    reordered index migrations (compare)

  • Nov 14 13:20
    niemyjski synchronize #452
  • Nov 14 13:20

    niemyjski on elastic7

    Added reindex cutoff date option (compare)

  • Nov 14 12:12
    niemyjski commented #465
  • Nov 14 11:39
    niemyjski synchronize #452
  • Nov 14 11:39

    niemyjski on elastic7

    Started conversion to ES7 Fix a bunch of errors More Few more fixes and 56 more (compare)

  • Nov 14 11:28
    niemyjski commented #465
  • Nov 14 11:27
    niemyjski closed #465
  • Nov 14 11:27

    niemyjski on master

    Fix #465 - Temporary remove myg… (compare)

  • Nov 14 09:27
    BrisWhite commented #461
  • Nov 13 15:14
    niemyjski commented #465
  • Nov 13 07:06
    squarezx commented #465
  • Nov 12 14:58
    niemyjski commented #461
Blake Niemyjski
@niemyjski
and what that did before
cause that no longer exists
Eric J. Smith
@ejsmith
that was making it so that if you had a nested property it would be available as blah: in search vs someobject.nested.blah
I think I read tha you have to do multifields or something instead now.
elastic/elasticsearch#6677
Blake Niemyjski
@niemyjski
ok
Sander Rijken
@srijken
crap, forgot to update the tests
at least its good that the build now fails when a testcase fails hehe
Blake Niemyjski
@niemyjski
:)
Eric J. Smith
@ejsmith
elastic/elasticsearch#11079
Blake Niemyjski
@niemyjski
so should we be doing copyto
Eric J. Smith
@ejsmith
yeah and setting that field to be not indexed.
Blake Niemyjski
@niemyjski
sigh
lol
ok
Eric J. Smith
@ejsmith
so I guess you have to create the top level properties for things that we have and then do copy_to on the nested ones.
Blake Niemyjski
@niemyjski
but what happens for ip
Eric J. Smith
@ejsmith
what about it?
Blake Niemyjski
@niemyjski
when you have multiple fields doing copyto
Eric J. Smith
@ejsmith
you can have multiple fields copy_to the same field
Blake Niemyjski
@niemyjski
ok
sucks that we can’t have dots in the name
names
gotta figure that out
Eric J. Smith
@ejsmith
you can
Blake Niemyjski
@niemyjski
ah
I’m pretty sure you cant
Eric J. Smith
@ejsmith
I just saw an example that had it.
Blake Niemyjski
@niemyjski

Invalid NEST response built from a unsuccesful low level call on PUT: /employees-v1

Audit trail of this API call:

  • BadResponse: Node: http://localhost:9200/ Took: 00:00:00.4679548

    ServerError: ServerError: 400Type: mapper_parsing_exception Reason: "Failed to parse mapping [employee]: Mapping definition for [companyId] has unsupported parameters: [index_name : company]" CausedBy: "Type: mapper_parsing_exception Reason: "Mapping definition for [companyId] has unsupported parameters: [index_name : company]""

    OriginalException: System.Net.WebException: The remote server returned an error: (400) Bad Request.

    at System.Net.HttpWebRequest.GetResponse()
    at Elasticsearch.Net.HttpConnection.RequestTReturn in C:\users\russ\source\elasticsearch-net\src\Elasticsearch.Net\Connection\HttpConnection.cs:line 138

    Request:

    <Request stream not captured or already read to completion by serializer. Set DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>

    Response:

    <Response stream not captured or already read to completion by serializer. Set DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>

                .String(f => f.Name(e => e.CompanyId).IndexName(Fields.Employee.CompanyId).Index(FieldIndexOption.NotAnalyzed))
way to even throw a dam compiler warning
0 warnings
Sander Rijken
@srijken
that looks nice
Eric J. Smith
@ejsmith
gotta do copy_to for that too… kind of sucks.
they said it was confusing I guess.
that error is a HELL of a lot better than the old errors.
we used to get a massive java stacktrace with the error burried in the middle of 1000s of lines of text.
Blake Niemyjski
@niemyjski
how the FUCK
Eric J. Smith
@ejsmith
?
Blake Niemyjski
@niemyjski
do you say copy to this field
but specify anaylzer option
I want to say don’t anaylze this and don’t index this field
Eric J. Smith
@ejsmith
you need to define the field that you are copy_to ‘ing
Blake Niemyjski
@niemyjski
you serious
Eric J. Smith
@ejsmith
yep
Blake Niemyjski
@niemyjski
this is going to make our defintions a nightmare
Eric J. Smith
@ejsmith
even though it doesn’t exist in the doc.
you have to define it and then do copy_to on the actual property.
and say not indexed on the real one too