seata confused about the documentation [important]

s8vozzvw  于 4个月前  发布在  其他
关注(0)|答案(1)|浏览(59)

I think there do not have a clear describe regard to seata component and their respective configration.
Yea, you guys wrote a documentation but it just describe every option's mean.
Yea, you guys impletment various of config and registy center but it's not clearly about their's usage.
But I do not recomment wrote a documentaion all in one.

Let's have a look about what happen
Fristly I download a seata server package and found there have 2 files about the configruation.
One is conf/application.yaml which one I think is a configuration for seata sever seems like our springcloud's application.yml.
One is script/config-center/config.txt which one is refer to seata offical documentation

question 1:
参数同步到配置中心使用demo
I did it.

And then It looks strange. My first impression of this is something maybe really wrong. but ,I don't know.
question 2:
There do not have a documentation about application.yaml Just have a example file .
seata.config.nacos.data-id for what?
Does this prove someting about question one ,I don't know.

seata:
  config:
    # support: nacos 、 consul 、 apollo 、 zk  、 etcd3
    type: file
    nacos:
      server-addr: 127.0.0.1:8848
      namespace:
      group: SEATA_GROUP
      username:
      password:
      context-path:
      ##if use MSE Nacos with auth, mutex with username/password attribute
      #access-key: ""
      #secret-key: ""
      data-id: seataServer.properties

I'm still confused about where this configuration should be placed,and when they will be loaded and use.

ijnw1ujt

ijnw1ujt1#

If I were you, I would also be equally confused. The community has not provided sufficient guidance on the configuration documentation. In older versions, Seata configuration could only use multiple independent small configuration items, while in newer versions, all-in-one configuration is supported, as seen in the seataServer.properties in your configuration file. Similarly, the documentation is outdated and lacks a systematic approach.

如果我是你,我也会同样困惑,这里确实是社区对于配置这块的文档引导做的不够好。在低版本中seata的配置只能使用多个独立的小配置项,在高版本中支持了支持了all in one的配置如你配置文件中的 seataServer.properties 。同样的文档老旧不够体系化。

相关问题