yuanlihan opened a new pull request #9883:
URL: https://github.com/apache/druid/pull/9883


   
   <img width="1374" alt="Screenshot 2020-05-05 at 15 47 27" 
src="https://user-images.githubusercontent.com/44718283/82133820-e0707d80-9822-11ea-8d79-18a5d6781e78.png";>
   
   
   ### Motivation
   This PR proposes to remove the `payload` field from table `sys.segments` 
mainly to handle performance issue caused by serializing object to JSON string.
   
   ### Drop alternative
   Add a projection rule for scanning table `sys.segment`.
   
   ### Operational impact
   Since the `payload` field has been already public documented, it's a little 
aggressive to remove it. But I would like to suppose that there may be rare 
possibility someone has a dependency on this field. The RESTful `api 
/druid/coordinator/v1/datasources/{dataSourceName}/segments/{segmentId} ` 
should be the priority option to retrieve segment metadata.
   
   This PR has:
   - [X] been self-reviewed.
   - [ ] added documentation for new or modified features or behaviors.
   - [ ] added Javadocs for most classes and all non-trivial methods. Linked 
related entities via Javadoc links.
   - [ ] added or updated version, license, or notice information in 
[licenses.yaml](https://github.com/apache/druid/blob/master/licenses.yaml)
   - [ ] added comments explaining the "why" and the intent of the code 
wherever would not be obvious for an unfamiliar reader.
   - [ ] added unit tests or modified existing tests to cover new code paths.
   - [ ] added integration tests.
   - [X] been tested in a test Druid cluster.
   <hr>
   
   ##### Key changed/added classes in this PR
    * `SystemSchema`
   


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

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