uber-go / dosa Goto Github PK

It's all through the code, and it's still to hard to explain. These terms are more easily understood.

While we're making this change, we should also add the appName (formerly namePrefix) to the CreateEnvironment (formerly CreateScope) call to improve our ability to route and/or name keyspaces based on both.

This issue has been opened automaticaly because we think you are using satori/uuid in your code. Unfortunately, satori/uuid has a critical defect where it doesn't generate random UUIDV4s satori/go.uuid#73 and should be replaced as the maintainer has been unresponsive for 5 months with the bug still open. Alternative packages you should consider: https://github.com/google/uuid https://github.com/pborman/uuid

This happens because the code that figures out the version assumes you are using git.

We need a makefile variable you can set if you know the version already so we can bake it into the built binary.

Just tried to go get and got this:

$ go get github.com/uber-go/dosa/cmd/dosa
# go.uber.org/yarpc/encoding/thrift
../../../go.uber.org/yarpc/encoding/thrift/inbound.go:119:12: undefined: protocol.Responder
../../../go.uber.org/yarpc/encoding/thrift/inbound.go:143:33: undefined: protocol.EnvelopeAgnosticProtocol
../../../go.uber.org/yarpc/encoding/thrift/inbound.go:161:15: undefined: protocol.EnvelopeV1Responder
../../../go.uber.org/yarpc/encoding/thrift/inbound.go:168:15: undefined: protocol.NoEnvelopeResponder

Hello,

I'm working with graph databases, in detail with Apache Tinkerpop. The Tinkerpop uses REST or websockets so internally the data structure are JSON structures, but mostly nested JSON objects with meta-information. On graph databases it is a good strategy to define a schema for vertices and edges (see for example Janusgraph).

In my use-case I'm using Java and Go, so it might be interesting for me, to support this project. But how can I start fo example to add the Tinkerpop support?

I'm happy to setup go.uber.org/dosa; it:

• Only contains uber branding in the import path, so no github
• Removes the - from the import path
• Is really short
• Lets you move the source later if you'd like

Once I do, you can use that import path everywhere.