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

InfluxDataPoint fields cannot be different types. #7

Closed
ghost opened this issue Feb 23, 2016 · 1 comment
Closed

InfluxDataPoint fields cannot be different types. #7

ghost opened this issue Feb 23, 2016 · 1 comment

Comments

@ghost
Copy link

ghost commented Feb 23, 2016

There may be situations where we have multiple fields that have different data types. For example we may have a integer value for responseTime and a string value for requestId,

The current data structure does not support this, as the fields are a dictionary<string, T> where T is the specified type.

@mvadu
Copy link
Contributor

mvadu commented Feb 24, 2016

@Scarfie This is more by design. My idea was to have type safety, where multiple fields of single type T are contained in single InfluxDataPoint<T>. As you can see from TestPostPointsAsync if you want to have an int and a string points in same measurement, you create multiple points (InfluxDatapoint<string> and InfluxDatapoint<int>) and set it to same measurement name. Then the PostPointsAsync combines them into single insert line protocol statement.

mvadu added a commit that referenced this issue Apr 13, 2016
Fixes #7 and #9, Support for multi type points, and long (int64). Also a breaking chnage the DB structure
mvadu added a commit that referenced this issue Apr 13, 2016
Fixes #7 and #9, Support for multi type points, and long (int64). Also a breaking chnage the DB structure
@mvadu mvadu closed this as completed in #10 Apr 13, 2016
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

1 participant