You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An xcontent abstraction on top how elasticsearch handles data (both parsing and generation). Inspired by JSON format (actually, one by one to json) with two default implementations: JSON, and XSON. XSON (maps to Content-Type application/xson) is an optimized binary representation of JSON.
In general, content in elasticsearch is broken down into the following:
Indexed content. In this case, the content type can be derived from the stream (thought can be set using Content-Type.
Request: Search, Count (query), and other request body allow for xContent data now. Again, the content type can be derived from the stream.
Response: The format of the response. Uses the Content-Type for this. If not available, and REST body is available, then tries to derive it from it. If not, defaults to JSON.
In Java, all custom builders (aside from index source) have been renamed. This include the query / filter builders. By default, they now generate xson format (the "user" is not aware of the format used, and xson is more optimized).
The text was updated successfully, but these errors were encountered:
An xcontent abstraction on top how elasticsearch handles data (both parsing and generation). Inspired by JSON format (actually, one by one to json) with two default implementations: JSON, and XSON. XSON (maps to Content-Type
application/xson
) is an optimized binary representation of JSON.In general, content in elasticsearch is broken down into the following:
Content-Type
.Content-Type
for this. If not available, and REST body is available, then tries to derive it from it. If not, defaults to JSON.In Java, all custom builders (aside from index source) have been renamed. This include the query / filter builders. By default, they now generate xson format (the "user" is not aware of the format used, and xson is more optimized).
The text was updated successfully, but these errors were encountered: