mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-22 21:05:23 +00:00
[DOCS] Removed API xrefs from Painless GSG
This commit is contained in:
parent
a2845c86fe
commit
f80799acc2
@ -174,13 +174,12 @@ POST hockey/player/1/_update
|
||||
==== Dates
|
||||
|
||||
Date fields are exposed as
|
||||
<<painless-api-reference-org-joda-time-ReadableDateTime, `ReadableDateTime`>>s
|
||||
`ReadableDateTime`
|
||||
so they support methods like
|
||||
<<painless-api-reference-org-joda-time-ReadableDateTime-getYear-0, `getYear`>>,
|
||||
and
|
||||
<<painless-api-reference-org-joda-time-ReadableDateTime-getDayOfWeek-0, `getDayOfWeek`>>.
|
||||
`getYear`,
|
||||
and `getDayOfWeek`.
|
||||
To get milliseconds since epoch call
|
||||
<<painless-api-reference-org-joda-time-ReadableInstant-getMillis-0, `getMillis`>>.
|
||||
`getMillis`.
|
||||
For example, the following returns every hockey player's birth year:
|
||||
|
||||
[source,js]
|
||||
@ -342,8 +341,7 @@ Java, leading to some trouble when it whitelists classes from the Java
|
||||
standard library. For example, in Java and Groovy, `Matcher` has two methods:
|
||||
`group(int)` and `group(String)`. Painless can't whitelist both of them methods
|
||||
because they have the same name and the same number of parameters. So instead it
|
||||
has <<painless-api-reference-Matcher-group-1, `group(int)`>> and
|
||||
<<painless-api-reference-Matcher-namedGroup-1, `namedGroup(String)`>>.
|
||||
has `group(int)` and `namedGroup(String)`.
|
||||
|
||||
We have a few justifications for this different way of dispatching methods:
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user