[Feature request] Drop field
Due to inattention, I have two fields, `rx_pkt` and `rx_packets`, each with a few million measurements, and I only need either of those. Is there an equivalent to the following SQL to get rid of a single field in InfluxDB? ``` sql alter table traffic drop `rx_pkt`, drop `tx_pkt` ```
Posted by dmke on Mar 29, 2016, 3:40 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
[Feature request] Drop field
Due to inattention, I have two fields, `rx_pkt` and `rx_packets`, each with a few million measurements, and I only need either of those. Is there an equivalent to the following SQL to get rid of a single field in InfluxDB? ``` sql alter table traffic drop `rx_pkt`, drop `tx_pkt` ```
Comments (0)
No comments yet. Start the discussion.