-
+
{
}
onChange={handleFromSectionChange}
/>
-
+
+ WHERE
+
{
withTemplateVariableOptions(getTagValues(key, measurement, policy, query.tags ?? [], datasource))
}
/>
-
+
{selectLists.map((sel, index) => (
-
+
Promise.resolve(getNewSelectPartOptions())}
@@ -150,9 +146,9 @@ export const Editor = (props: Props): JSX.Element => {
onAppliedChange(removeSelectPart(query, partIndex, index));
}}
/>
-
+
))}
-
+
getNewGroupByPartOptions(query, getTagKeys)}
@@ -167,8 +163,8 @@ export const Editor = (props: Props): JSX.Element => {
onAppliedChange(removeGroupByPart(query, partIndex));
}}
/>
-
-
+
+
{
onAppliedChange({ ...query, tz });
}}
/>
-
+
+ ORDER BY TIME
+
{
onAppliedChange({ ...query, orderByTime: v });
}}
/>
-
+
{/* query.fill is ignored in the query-editor, and it is deleted whenever
query-editor changes. the influx_query_model still handles it, but the new
approach seem to be to handle "fill" inside query.groupBy. so, if you
- have a panel where in the json you have query.fill, it will be appled,
+ have a panel where in the json you have query.fill, it will be applied,
as long as you do not edit that query. */}
-
+
{
onAppliedChange({ ...query, limit });
}}
/>
-
+
+ SLIMIT
+
{
onAppliedChange({ ...query, slimit });
}}
/>
-
-
+
+
{
@@ -215,7 +215,9 @@ export const Editor = (props: Props): JSX.Element => {
/>
{query.resultFormat !== 'table' && (
<>
-
+
+ ALIAS
+
{
/>
)}
-
+