Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

Consider adding beaconId to the Beacon response #52

Closed
mfiume opened this issue May 31, 2016 · 1 comment
Closed

Consider adding beaconId to the Beacon response #52

mfiume opened this issue May 31, 2016 · 1 comment
Milestone
0.4

Comments

@mfiume
Copy link
Contributor

mfiume commented May 31, 2016

The response currently includes datasetId, but not beaconId. Having a beaconId in the response would help resolve the source of the query in applications that may query multiple Beacons simultaneously.
@mfiume mfiume modified the milestones: 0.3, 0.4 May 31, 2016
@mcupak
Copy link
Contributor

mcupak commented May 31, 2016

I think this was misfiled, beacon ID is in the response:

https://github.com/ga4gh/beacon-team/blob/develop/src/main/resources/avro/beacon.avdl#L243

Closing.

@mcupak mcupak closed this as completed May 31, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.4
Development

No branches or pull requests
2 participants
@mcupak @mfiume