[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618255#comment-17618255
 ] 

Martin Fischer edited comment on ASTERIXDB-2632 at 10/16/22 11:42 AM:
----------------------------------------------------------------------

I've stumbled upon a bug related to this: when using e.g. the new web interface 
on 19006 or when choosing "JSON (formatted)" as output format on the legacy web 
interface on 19001, then the result set is always reported as empty as soon as 
it includes a day_time_duration. This can also be observed when looking at the 
sample preview for datasets on the new interface: if the dataset's first record 
contains a day_time_duration then the dataset is reported to have no entries.

Can easily be reproduced using the following query:

{{DROP DATAVERSE Test IF EXISTS;}}

{{CREATE DATAVERSE Test;}}

{{USE Test;}}

{{{}CREATE TYPE Type1 AS {{}}}{{{}auto_id: uuid{}}}{{{}}{}}}{{{};{}}}

{{CREATE DATASET DS(Type1) PRIMARY KEY auto_id AUTOGENERATED;}}

{{INSERT INTO DS ([\{"dtd": day_time_duration("-PT328M")}]);}}

Refer to the screenshots for the weird behavior that follows.


was (Author: JIRAUSER296966):
I've stumbled upon a bug related to this: when using e.g. the new web interface 
on 19006 or when choosing "JSON (formatted)" as output format on the legacy web 
interface on 19001, then the result set is always reported as empty as soon as 
it includes a day_time_duration. This can also be observed when looking at the 
sample preview for datasets on the new interface: if the dataset's first record 
contains a day_time_duration then the dataset is reported to have no entries.

Can easily be reproduced using the following query:

{{DROP DATAVERSE Test IF EXISTS;}}

{{CREATE DATAVERSE Test;}}

{{USE Test;}}

{{{}CREATE TYPE Type1 AS {{}}}{{{}auto_id: uuid{}}}{{{}}{}}}{{{};{}}}

{{CREATE DATASET DS(Type1) PRIMARY KEY auto_id AUTOGENERATED;}}

{{INSERT INTO DS (["dtd": day_time_duration("-PT328M")}]);}}

Refer to the screenshots for the weird behavior that follows.

> Unable to handle data type day_time_duration
> --------------------------------------------
>
>                 Key: ASTERIXDB-2632
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2632
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: *DB - AsterixDB
>    Affects Versions: 0.9.4.1, 0.9.5
>            Reporter: Sandeep Gupta
>            Assignee: Dmitry Lychagin
>            Priority: Minor
>         Attachments: Screen Shot 2019-09-10 at 11.44.16 AM.png, Screen Shot 
> 2019-09-10 at 11.54.10 AM.png, Screen Shot 2019-09-11 at 2.12.25 PM.png, 
> Screenshot_20221016_133228.png, Screenshot_20221016_133302.png, 
> Screenshot_20221016_133318.png, Screenshot_20221016_133329.png
>
>
> These queries are failing:
>  
> SELECT day_time_duration("-PT328M") as `myduration`;
> SELECT day_time_duration('P439D') as `myduration`;
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to