[GitHub] [pinot] mcvsubbu commented on pull request #10655: API to expose the contract/rules imposed by pinot on tableConfig

["mcvsubbu (via GitHub)" <gi...@apache.org>]

mcvsubbu commented on PR #10655:
URL: https://github.com/apache/pinot/pull/10655#issuecomment-1518320254

   I understand the re-org of code to have metadata on fieldSpec, but why expose this via API? How will a user of Pinot make use of this API?
   
   Should we call the API `/schemata/fieldSpec`? Is this endpoint always going to be some general stuff (i.e. tableName, segmentName, etc. are not an argument)? 


-- 
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: commits-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org