abhishekrb19 commented on issue #17361:
URL: https://github.com/apache/druid/issues/17361#issuecomment-2444929447

   Sorry for the delay. It looks like there are at least two separate issues 
here:
   
   1. The `/introspect` endpoint not returning valid JSON (this issue). The 
[fix](https://github.com/apache/druid/issues/17361#issuecomment-2421820169) for 
this should be straightforward.
   
   2. A separate issue with the `/version` endpoint. It seems like 
@ashwintumma23 has identified a documentation gap, which could be worth 
addressing. I agree that the version returned in the `/version` endpoint is 
confusing—it currently returns the cache scheduler’s internal version rather 
than the user-facing version. We could clarify this unambiguously in the 
documentation to avoid any confusion: 
https://druid.apache.org/docs/latest/querying/lookups-cached-global/#introspection.
   
   If we also want to address the discrepancy between the multiple versions, we 
could expose the user-facing version in addition to the cache scheduler’s 
version by adding a new field to the response map for compatibility: 
https://github.com/apache/druid/blob/master/extensions-core/lookups-cached-global/src/main/java/org/apache/druid/query/lookup/NamespaceLookupIntrospectHandler.java#L79.
 To retrieve the user-facing lookup version, we may need to access that 
information from `LookupExtractorFactoryContainer`.
   
   If there's more discussion required for the second issue, I'd suggest 
creating a separate targeted issue so it's easier to track.
   
   Please let me know if you'd like to take a stab at it.
   
   


-- 
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