Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 01:09
    billgao87 starred exceptionless/Exceptionless
  • Sep 20 13:20

    niemyjski on elastic7

    Fixed more unit tests (compare)

  • Sep 20 12:11
    niemyjski commented #447
  • Sep 20 07:42
    ZhiqiangTao commented #447
  • Sep 19 22:56

    niemyjski on elastic7

    bumped major and deps (fixed te… (compare)

  • Sep 19 14:20

    niemyjski on elastic7

    Fixed all issues with the event… (compare)

  • Sep 19 07:04
  • Sep 19 04:49
  • Sep 19 03:32
  • Sep 18 12:46
    LydellM commented #448
  • Sep 18 12:38
    niemyjski labeled #448
  • Sep 18 12:37
    niemyjski closed #448
  • Sep 18 12:37
    niemyjski commented #448
  • Sep 18 12:37
    niemyjski commented #448
  • Sep 18 12:35
    niemyjski commented #447
  • Sep 18 07:09
    ZhiqiangTao closed #447
  • Sep 18 05:31
    leehomlee starred exceptionless/Exceptionless
  • Sep 18 03:17
  • Sep 18 02:13

    niemyjski on elastic7

    More ES7 Changes (compare)

  • Sep 17 20:34
    LydellM opened #448
Blake Niemyjski
@niemyjski
?
Eric J. Smith
@ejsmith
yeah, exactly… this will be huge for that.
I’ve seen tons of customers get their entire plan eaten up in a few hours.
Blake Niemyjski
@niemyjski
@ejsmith
want to work with me on these tests for 2.0 :)
just the foundatio.repository tests
Sander Rijken
@srijken
@niemyjski I think the question on the UI update was for @ejsmith as well?
Blake Niemyjski
@niemyjski
yeah
I think we are safe with pushing it out there
Eric J. Smith
@ejsmith
I gotta finish my AWS stuff over the next couple days before I move on to ES2.
Blake Niemyjski
@niemyjski
ok
gotta figure out the stuff on just_name
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.