Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 09:53
    codecov[bot] commented #1071
  • 09:53
    codecov[bot] commented #1071
  • 09:49
    codecov[bot] commented #1071
  • 09:49
    codecov[bot] commented #1071
  • 09:49
    jjcollinge synchronize #1071
  • 09:27
    codecov[bot] commented #1071
  • 09:27
    codecov[bot] commented #1071
  • 09:26
    jjcollinge synchronize #1071
  • 08:07
    jjcollinge commented #1071
  • 08:07
    jjcollinge edited #1071
  • 08:06
    jjcollinge edited #1071
  • 08:04
    codecov[bot] commented #1155
  • 08:04
    codecov[bot] commented #1155
  • 07:56
    codecov[bot] commented #1155
  • 07:56
    codecov[bot] commented #1155
  • 07:56
    1046102779 synchronize #1155
  • 05:07
    cshi0 commented #962
  • 05:05
    codecov[bot] commented #962
  • 05:05
    codecov[bot] commented #962
  • 05:05
    cshi0 synchronize #962
Young Bu Park
@youngbupark
Hello!
Tam Mach
@sayboras
hi
Anubhav Mishra
@anubhavmishra
Hello! :wave:
Anubhav Mishra
@anubhavmishra
@youngbupark builds all passing now! dapr/components-contrib#84
I might make a PR to docs to add a how-to
Young Bu Park
@youngbupark
@anubhavmishra ok cool. thanks for the contribution. I will look at your pr :)
Anubhav Mishra
@anubhavmishra
no rush!
thanks for reviewing it.
Abhishek Gupta
@abhirockzz
Some observations reg "Expected state store behaviors" as per https://github.com/dapr/docs/blob/master/reference/api/state.md#expected-state-store-behaviors
  • Currently this is not really enforced via an interface
  • Implementation needs to map it to respective state store concepts (which if fine, but tricky at times)
  • The implementation itself requires "if-else" for concurrency and consistency, and then choosing the right "API call"
I was trying to play around with a state store implementation for couchbase and these ^ thoughts popped up during that process
Abhishek Gupta
@abhirockzz
I wonder if it's possible to make this easier? Also, I see that some of the state store implementations do not take this (consistency, concurrency etc.) into account
Yaron Schneider
@yaron2
Yes, that's why the consistency/concurrency are optional as part of the request. A state store does not have to implement them. We will extend the docs on supported state stores to extend the table and show which stores enable those features.
That doc is outdated.. it references a spec that is not in use anymore. These behaviors are not required.
Abhishek Gupta
@abhirockzz
Thanks. For Dapr state stores, consistency is either "eventual" or "strong", but that is not the case with every database. Classic e.g. is Cassandra which has the equivalent of ALL (all replicas) or ANY (at least one node) for "strong" and "eventual" respectively, but also has other consistency levels e.g. QUORUM, ONE, TWO etc. How can state store implementations account for these?
Yaron Schneider
@yaron2
Because Dapr defines eventual or strong, a state store can either account for these two, or none. In order to account for extra settings, implementations can use the metadata fields that can be set with every state request, and map these to the specific implementation of the store.
Tam Mach
@sayboras
@yaron2 @youngbupark the build is passing now dapr/components-contrib#104
Tam Mach
@sayboras
stather
@stather
Would an Azure storage queue component be a useful addition?
Tam Mach
@sayboras
@youngbupark will be great if I can follow some steps (dapr/components-contrib#44)
Joni Collinge
@jjcollinge
Hey, is anybody free to run a quick test for me to validate a fix on this PR (dapr/components-contrib#186). It looks to address a bug in the Azure ServiceBus pubsub component when the network disconnects. If so, let me know and I can explain in more detail over DM (p.s. you will need an Azure ServiceBus to use).
Young Bu Park
@youngbupark
@sayboras Please review this pr - dapr/components-contrib#202
madhugilla
@madhugilla
hello, created a new output bining component for alicloud objectstorage service and raised a pull rquest, this is my firsttime contributing to dapr, dapr/components-contrib#278. please let me know. Created tests, updated the dapr file (main.go) and tested with alicloud.
madhugilla
@madhugilla
@yaron2 ran "go mod tidy" and fixed a comment and pusehed the changes for pull request dapr/components-contrib#278
madhugilla
@madhugilla
@yaron2 pls let me know if i need to do anything else from my side. thank you
madhugilla
@madhugilla
Thank you @yaron2 ..
Mayank Kumar
@kumaya
Hi All, I plan to create a new pub-sub for MQTT. This is my first time contributing to dapr/components-contrib. I have opened an issue dapr/components-contrib#326. Please let me know.