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

ASF GitHub Bot commented on NIFI-2900:
--------------------------------------

Github user mcgilman commented on the issue:

    https://github.com/apache/nifi/pull/1136
  
    @mike42 - Thanks for checking out Apache NiFi and looking to make 
improvements here. We just released version 1.0.0 so we don't have another 
major release scheduled in the immediate future. We could certainly look to 
update the endpoints to return these new values in addition to the existing 
ones (which could then be marked as deprecated). Or we could investigate a 
means for versioning the API so that existing clients wouldn't break and new 
clients could utilize the new endpoints. Though it may make sense to do this 
work when we add i18n support throughout the application which will likely 
require either a major NiFi version change or supporting multiple versions of 
the REST API concurrently.
    
    Regardless what additional work we identify here, I believe the work that 
was discussed with @simplesteph needs to happen as the documentation is 
currently misreporting the actual data type of these fields.


> DateTime API Endpoints don't respect RFC 3339
> ---------------------------------------------
>
>                 Key: NIFI-2900
>                 URL: https://issues.apache.org/jira/browse/NIFI-2900
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.0.0
>            Reporter: Stephane Maarek
>
> Hi,
> the endpoint /flow/process-group/id is supposed to return lastRefreshed as 
> part of ProcessGroupFlowDTO as a DateTime, as indicated here:
> lastRefreshed string (date-time)      optional        The time the flow for 
> the process group was last refreshed.
> as it currently stands, what I am getting doesn't look like a timestamp:
> "lastRefreshed":"14:02:46 AEDT"
> I'm not sure how much of the overall API is affected
> Edit:
> Actually, it seems every date a "date-time" is created we expect the format 
> "HH:mm:ss z".
> As per the OpenAPI specs, if a field is annotated "date-time", it should 
> respect the RFC 3339 convention 
> (https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types).
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to