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

Create single parquet schema for autopush #874

Closed
bbangert opened this issue Apr 19, 2017 · 0 comments
Closed

Create single parquet schema for autopush #874

bbangert opened this issue Apr 19, 2017 · 0 comments
Assignees
@bbangert
Milestone
2017Q2-2.1 Report...

Comments

@bbangert
Copy link
Member

The PR here (#832) should be modified and re-opened by our team with a single schema. Starting from the code in this closed PR is a good start, and instead of separate schemas for each index as the PR has, a single schema including all the fields we want to capture should be made.

We could do this by starting from the more thorough of the existing schemas, and just ensure it has all the optional fields from both places.
@bbangert bbangert added the ready label Apr 19, 2017
@bbangert bbangert mentioned this issue Apr 19, 2017
Closed
@bbangert bbangert self-assigned this Apr 19, 2017
bbangert added a commit that referenced this issue Apr 27, 2017
@bbangert
feat: add parquet unified schema and cleanup logging messages
ec271c8 
Adds a unified parquet stream for all log messages with a message
matcher for necessary endpoint and connection node messages.
Logging fields were cleaned up for consistency and status code
logging uses a 0 instead of "" to avoid mixing types.

Closes #874, #882
@bbangert bbangert mentioned this issue Apr 27, 2017
Merged
bbangert added a commit that referenced this issue Apr 27, 2017
@bbangert
feat: add parquet unified schema and cleanup logging messages
291ab7c 
Adds a unified parquet stream for all log messages with a message
matcher for necessary endpoint and connection node messages.
Logging fields were cleaned up for consistency and status code
logging uses a 0 instead of "" to avoid mixing types.

Closes #874, #882
bbangert added a commit that referenced this issue Apr 27, 2017
@bbangert
feat: add parquet unified schema and cleanup logging messages
59ce55c 
Adds a unified parquet stream for all log messages with a message
matcher for necessary endpoint and connection node messages.
Logging fields were cleaned up for consistency and status code
logging uses a 0 instead of "" to avoid mixing types.

Closes #874, #882
bbangert added a commit that referenced this issue Apr 27, 2017
@bbangert
feat: add parquet unified schema and cleanup logging messages
80b33d0 
Adds a unified parquet stream for all log messages with a message
matcher for necessary endpoint and connection node messages.
Logging fields were cleaned up for consistency and status code
logging uses a 0 instead of "" to avoid mixing types.

Closes #874, #882
bbangert added a commit that referenced this issue Apr 27, 2017
@bbangert
feat: add parquet unified schema and cleanup logging messages
63d2981 
Adds a unified parquet stream for all log messages with a message
matcher for necessary endpoint and connection node messages.
Logging fields were cleaned up for consistency and status code
logging uses a 0 instead of "" to avoid mixing types.

Closes #874, #882
@bbangert bbangert mentioned this issue Apr 27, 2017
Closed
5 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bbangert bbangert

Labels
None yet
Projects
None yet
Milestone
2017Q2-2.1 Report generated twice a m...
Development

No branches or pull requests
1 participant
@bbangert