Skip to content

Another truthy falsy issue, this time in the allField #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
clintongormley opened this issue Mar 20, 2010 · 2 comments
Closed

Another truthy falsy issue, this time in the allField #76

clintongormley opened this issue Mar 20, 2010 · 2 comments

Comments

@clintongormley
Copy link
Contributor

Hiya

This statement cause a null pointer exception, but succeeds when enabled is true:

curl -XPUT 'http://127.0.0.2:9200/ia_object/site/_mapping?ignoreConflicts=false'  -d '
{
   "allField" : {
      "store" : "yes",
      "termVector" : "with_positions_offsets",
      "enabled" : 1
   },
   "properties" : {
      "created" : {
         "format" : "yyyy-MM-dd HH:mm:ss",
         "type" : "date"
      },
      "ancestor_ids" : {
         "type" : "long"
      },
      "status" : {
         "index" : "not_analyzed",
         "type" : "string"
      },
      "last_modified" : {
         "format" : "yyyy-MM-dd HH:mm:ss",
         "type" : "date"
      },
      "id" : {
         "type" : "long"
      },
      "parent_id" : {
         "type" : "long"
      },
      "creator_id" : {
         "nullValue" : 0,
         "type" : "long"
      }
   }
}
'
@kimchy
Copy link
Member

kimchy commented Mar 20, 2010

parse correct enabled flag on all field when passed as number, closed by fa1071d

@clintongormley
Copy link
Contributor Author

Fixed++

rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
Update to elasticsearch 1.3.0
Move to java 1.7

Related to elastic#67.
Closed elastic#76.

(cherry picked from commit 2303932)
maabernethy pushed a commit to maabernethy/elasticsearch that referenced this issue Mar 20, 2017
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
With this commit we expose a new track parameter `starting_point` for
the challenge `index-logs-fixed-daily-volume`. It has previously assumed
a certain date but for consistency with
`index-and-query-logs-fixed-daily-volume` we now expose a track
parameter for this date.
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
With this commit we set:

* `cache.recycler.page.limit.heap`: 13.5%
* `cache.recycler.page.weight.bytes`: 2

which allocates more byte[] pages which are needed for our NIO
transport.

Closes elastic#74
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants