Re: REST API TIMESTAMP

[Вячеслав Коптилин]

Hello,

I'll just duplicate the answer from
https://stackoverflow.com/questions/73703680/apache-ignite-rest-api-timestamp-format
(Thanks to Igor Belyakov!)

The issue is related to the default locale provider change in the Java 9+,
see JEP 252 <https://openjdk.org/jeps/252>.

As a workaround, you can set the next option to enable behavior compatible
with Java 8: -Djava.locale.providers=COMPAT
Thanks,
S.


чт, 1 сент. 2022 г. в 10:28, Dren Butković :

>
> Example of timestamp data, difference is in "," after year.
>
> Ignite 2.7.6  Java 8   ->"Sep 18, 2019 12:57:35 PM"
> Ignite 2.13  Java 11  ->"Aug 31, 2022, 12:43:44 PM"
>
>
> On Thu, Sep 1, 2022 at 9:03 AM Dren Butković 
> wrote:
>
>> Hi,
>>
>> I have upgraded Ignite 2.7.6 on Java 8 to Ignite 2.13 on Java 11.
>> In the REST API response the timestamp format has changed.
>> Locale and all other ENV variables on the host are equal.
>>
>> Is there a possibility to define the format of the timestamp output in
>> the Ignite configuration?
>>
>> Best regards
>>
>> Dren Butković
>>
>

Re: REST API TIMESTAMP

[Dren Butković]

Example of timestamp data, difference is in "," after year.

Ignite 2.7.6  Java 8   ->"Sep 18, 2019 12:57:35 PM"
Ignite 2.13  Java 11  ->"Aug 31, 2022, 12:43:44 PM"


On Thu, Sep 1, 2022 at 9:03 AM Dren Butković 
wrote:

> Hi,
>
> I have upgraded Ignite 2.7.6 on Java 8 to Ignite 2.13 on Java 11.
> In the REST API response the timestamp format has changed.
> Locale and all other ENV variables on the host are equal.
>
> Is there a possibility to define the format of the timestamp output in the
> Ignite configuration?
>
> Best regards
>
> Dren Butković
>

REST API TIMESTAMP

[Dren Butković]

Hi,

I have upgraded Ignite 2.7.6 on Java 8 to Ignite 2.13 on Java 11.
In the REST API response the timestamp format has changed.
Locale and all other ENV variables on the host are equal.

Is there a possibility to define the format of the timestamp output in the
Ignite configuration?

Best regards

Dren Butković