You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/06/04 07:13:29 UTC

[GitHub] [pulsar] yujun32 opened a new issue #7166: I didnt find the Schema strategy I wanted

yujun32 opened a new issue #7166:
URL: https://github.com/apache/pulsar/issues/7166


   I need a Schema strategy like this:
        Producter can add fields based on business development, but old fields cannot be deleted and modified; (like protobuf).
        Consumers can consume all versions of data with various versions of Schema, and will lack new fields that are newer than the current version.
   
        I found the pulsar documentation. There is no such Schema strategy that only allows adding fields, and existing fields cannot be deleted and modified, and Consumer can consume all version data without upgrading.


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [pulsar] yujun32 removed a comment on issue #7166: I didnt find the Schema strategy I wanted

Posted by GitBox <gi...@apache.org>.
yujun32 removed a comment on issue #7166:
URL: https://github.com/apache/pulsar/issues/7166#issuecomment-640135151


   > [https://pulsar.apache.org/docs/en/schema-evolution-compatibility/#how-does-pulsar-support-schema-evolution ](https://pulsar.apache.org/docs/en/schema-evolution-compatibility/#how-does-pulsar-support-schema-evolution)
   > @ yujun32似乎您想要一个`BACKWARD_TRANSITIVE`？
   
   Thank you for answering,
   
   BACKWARD_TRANSITIVE is still a bit different from the strategy I want:
   1. Fields can only be added but not modified or deleted.
   2. Consumer can consume the latest data without upgrading.
   These two points are just the principles that our other services follow, so that the design rules will help our security upgrade and fault tolerance


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [pulsar] yujun32 commented on issue #7166: I didnt find the Schema strategy I wanted

Posted by GitBox <gi...@apache.org>.
yujun32 commented on issue #7166:
URL: https://github.com/apache/pulsar/issues/7166#issuecomment-640135232


   > https://pulsar.apache.org/docs/en/schema-evolution-compatibility/#how-does-pulsar-support-schema-evolution
   > @yujun32 Seems you want a `BACKWARD_TRANSITIVE`?
   
   
   Thank you for answering,
   
   BACKWARD_TRANSITIVE is still a bit different from the strategy I want:
   1. Fields can only be added but not modified or deleted.
   2. Consumer can consume the latest data without upgrading.
   These two points are just the principles that our other services follow, so that the design rules will help our security upgrade and fault tolerance


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [pulsar] Huanli-Meng commented on issue #7166: I didnt find the Schema strategy I wanted

Posted by GitBox <gi...@apache.org>.
Huanli-Meng commented on issue #7166:
URL: https://github.com/apache/pulsar/issues/7166#issuecomment-651458475


   @jiazhai , any more process about this issue?


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [pulsar] jiazhai commented on issue #7166: I didnt find the Schema strategy I wanted

Posted by GitBox <gi...@apache.org>.
jiazhai commented on issue #7166:
URL: https://github.com/apache/pulsar/issues/7166#issuecomment-639212325


   https://pulsar.apache.org/docs/en/schema-evolution-compatibility/#how-does-pulsar-support-schema-evolution
   @yujun32 Seems you want a `BACKWARD_TRANSITIVE`?


----------------------------------------------------------------
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:
users@infra.apache.org

[GitHub] [pulsar] yujun32 commented on issue #7166: I didnt find the Schema strategy I wanted

Posted by GitBox <gi...@apache.org>.
yujun32 commented on issue #7166:
URL: https://github.com/apache/pulsar/issues/7166#issuecomment-640135151


   > [https://pulsar.apache.org/docs/en/schema-evolution-compatibility/#how-does-pulsar-support-schema-evolution ](https://pulsar.apache.org/docs/en/schema-evolution-compatibility/#how-does-pulsar-support-schema-evolution)
   > @ yujun32似乎您想要一个`BACKWARD_TRANSITIVE`？
   
   Thank you for answering,
   
   BACKWARD_TRANSITIVE is still a bit different from the strategy I want:
   1. Fields can only be added but not modified or deleted.
   2. Consumer can consume the latest data without upgrading.
   These two points are just the principles that our other services follow, so that the design rules will help our security upgrade and fault tolerance


----------------------------------------------------------------
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:
users@infra.apache.org