Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify what fields in models are required. #2

Open
mohsen1 opened this issue Jan 10, 2016 · 5 comments
Open

Clarify what fields in models are required. #2

mohsen1 opened this issue Jan 10, 2016 · 5 comments

Comments

@mohsen1
Copy link
Contributor

mohsen1 commented Jan 10, 2016

No description provided.

@drolando
Copy link

drolando commented Oct 8, 2018

@adriancole bump. zipkin2-api.yaml says which fields you can leave absent. zipkin-api.yaml doesn't say anything about it.

Since they're not listed as required, I'd assume everything is optional and I can just avoid it. Whereas you comments on Yelp/py_zipkin#102 seem to suggest even in JSON I'd need to default port to 0 and serviceName to ""

@codefromthecrypt
Copy link
Member

technically you are right.. we (I) didn't spend any time going back to discuss v1 in the spec, hoping people stop using it :)

anyway I will put some notes down

@codefromthecrypt
Copy link
Member

codefromthecrypt commented Oct 9, 2018 via email

@codefromthecrypt
Copy link
Member

#54 for v1

I'll just make the change directly to v2 as only 2 fields are required though it would be silly to only serialize traceId, spanId

@codefromthecrypt
Copy link
Member

oops v2 format already says so..

    required:
      - traceId
      - id

codefromthecrypt pushed a commit that referenced this issue Oct 9, 2018
codefromthecrypt pushed a commit that referenced this issue Dec 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants