Akanksha-kedia opened a new pull request, #17709:
URL: https://github.com/apache/pinot/pull/17709

   …meseries responses
   
   - Add sendTimeSeriesRequestRaw method to handle timeseries responses without 
parsing as BrokerResponseNative
   - Update sendTimeSeriesRequestToBroker to use raw forwarding for both GET 
and POST endpoints
   - Fix GET endpoint method signature to use proper 
executeTimeSeriesQueryCatching parameters
   - Ensures controller preserves broker's PinotBrokerTimeSeriesResponse 
structure with status field
   - Resolves test failure: 'Status field should not be null in timeseries 
query response'
   
   The issue was that controller was incorrectly trying to parse timeseries 
responses as BrokerResponseNative and add execution time, but timeseries 
responses use PinotBrokerTimeSeriesResponse with different structure. This fix 
preserves the original Prometheus-compatible response format from the broker.
   
   Instructions:
   1. The PR has to be tagged with at least one of the following labels (*):
      1. `feature`
      2. `bugfix`
      3. `performance`
      4. `ui`
      5. `backward-incompat`
      6. `release-notes` (**)
   2. Remove these instructions before publishing the PR.
    
   (*) Other labels to consider:
   - `testing`
   - `dependencies`
   - `docker`
   - `kubernetes`
   - `observability`
   - `security`
   - `code-style`
   - `extension-point`
   - `refactor`
   - `cleanup`
   
   (**) Use `release-notes` label for scenarios like:
   - New configuration options
   - Deprecation of configurations
   - Signature changes to public methods/interfaces
   - New plugins added or old plugins removed
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to