-
Notifications
You must be signed in to change notification settings - Fork 32
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
Comments
@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 |
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 |
ps you don't need to default port to 0.. unless I had a brain cramp I
thought I said please don't default it to zero :D
…On Tue, Oct 9, 2018 at 2:21 AM Daniele ***@***.***> wrote:
@adriancole <https://github.com/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
<Yelp/py_zipkin#102> seem to suggest even in JSON
I'd need to default port to 0 and serviceName to ""
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAD610dQZTZFiGnyp-5VPv2m6frSlZaPks5ui5emgaJpZM4HB64u>
.
|
#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 |
oops v2 format already says so..
|
No description provided.
The text was updated successfully, but these errors were encountered: