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 2019/05/26 09:36:18 UTC

[GitHub] [pulsar] Inilien edited a comment on issue #4199: documentation: unclear how to use Pulsar IO

Inilien edited a comment on issue #4199: documentation: unclear how to use Pulsar IO
URL: https://github.com/apache/pulsar/issues/4199#issuecomment-495983977
 
 
   @sijie yes, thank you  
   Considering yaml configuration I found [this section](https://pulsar.apache.org/docs/en/pulsar-admin/#source) of docummentation - the [create](https://pulsar.apache.org/docs/en/pulsar-admin/#create-4) command accepts yaml configuration file which is I assume is exactly the file from this [example](https://pulsar.apache.org/docs/en/io-managing/#configuring-connectors) which I linked in the first message in the thread. (I don't know why I couldn't find this earlier... sorry)  
   
   It is still unclear if it is possible to specify custom serialization/deserialization logic for sinks and sources. From your previous answer I assumed that Pulsar IO doesn't support any SerDe logic but in [source create](https://pulsar.apache.org/docs/en/pulsar-admin/#create-4) and [sink create](https://pulsar.apache.org/docs/en/pulsar-admin/#create-3) I found these  `--deserialization-classname` and  `--custom-serde-inputs`  parameters respectfully. Could they be used to serialize data ingested into Pulsar into protobuf format in source connectors and deserialize from protobuf in sink connectors?
   

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


With regards,
Apache Git Services