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

Better migration path for users switching to tags #77

Open
bryanmikaelian opened this issue Apr 7, 2017 · 1 comment
Open

Better migration path for users switching to tags #77

bryanmikaelian opened this issue Apr 7, 2017 · 1 comment
Assignees
@jderrett @bryanmikaelian
Labels
2.0.x+ proposal

Comments

@bryanmikaelian
Copy link
Contributor

@jderrett and I have been talking and there have been some bumps in the road for users migrating from 0.1.7 to 2.x.x. We are considering making a change to the writeToLegacy behavior that would stop writes to the new API endpoint unless tags exist on the measurement if writeToLegacy is true. This config option will continue to be defaulted to false
@bryanmikaelian bryanmikaelian added this to the 2.x.x: Tagged Measurements milestone Apr 7, 2017
@mbeale
Copy link
Contributor

mbeale commented Jul 11, 2017

The only issue would be if they have top level tags. When sending the measurement if may be just foo without tags but the user may be expecting the top level tags to be attached to the measurement

@bryanmikaelian bryanmikaelian removed this from the 2.0.x: Tagged Measurements milestone Oct 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jderrett jderrett

@bryanmikaelian bryanmikaelian

Labels
2.0.x+ proposal
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jderrett @bryanmikaelian @mbeale