Add future of flux page and notifications (#5484)
* add future of flux page, update future of flux notification, add exclude functionality to notifications * Apply suggestions from code review Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com> * updated formatting and tense --------- Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>pull/5479/head^2
Scott Anderson
GitHub
parent
0895069789
commit
54de71013d
|
|
@ -24,11 +24,26 @@ function showNotifications () {
|
|||
return false;
|
||||
}
|
||||
|
||||
function excludePage (path, exclude) {
|
||||
if (exclude[0].length > 0) {
|
||||
for (let i = 0; i < exclude.length; i++) {
|
||||
if (path.includes(exclude[i])) {
|
||||
return true;
|
||||
}
|
||||
}
|
||||
}
|
||||
return false;
|
||||
}
|
||||
|
||||
var scope = $(this).data('scope').split(',');
|
||||
var exclude = $(this).data('exclude').split(',');
|
||||
var pageInScope = inScope(window.location.pathname, scope);
|
||||
var pageExcluded = excludePage(window.location.pathname, exclude);
|
||||
var notificationRead = notificationIsRead(notificationID(this), 'message');
|
||||
|
||||
if (pageInScope && !notificationRead) {
|
||||
console.log(pageExcluded)
|
||||
|
||||
if (pageInScope && !pageExcluded && !notificationRead) {
|
||||
$(this).show().animate({ right: 0, opacity: 1 }, 200, 'swing');
|
||||
}
|
||||
});
|
||||
|
|
|
|||
|
|
@ -39,6 +39,9 @@
|
|||
border-top: 1px dotted rgba($g20-white, .5);
|
||||
padding-top: 1.25rem;
|
||||
}
|
||||
|
||||
&:last-child {margin-bottom: 0;}
|
||||
p:last-child {margin-bottom: 0;}
|
||||
}
|
||||
|
||||
.notification-content {
|
||||
|
|
|
|||
|
|
@ -0,0 +1,51 @@
|
|||
---
|
||||
title: The future of Flux
|
||||
description: >
|
||||
Flux is in maintenance mode and is not supported in InfluxDB v3.
|
||||
This decision was based on the broad demand for native SQL and the continued
|
||||
growth and adoption of InfluxQL.
|
||||
menu:
|
||||
flux_v0_ref:
|
||||
name: Future of Flux
|
||||
weight: 15
|
||||
---
|
||||
|
||||
Flux is in maintenance mode and is not supported in InfluxDB v3 due to the broad
|
||||
demand for native SQL and the continued growth and adoption of InfluxQL.
|
||||
|
||||
InfluxData continues to support Flux for InfluxDB 1.x and 2.x, and you can
|
||||
continue using it without changing your code.
|
||||
If interested in transitioning to InfluxDB v3 and you want to future-proof your
|
||||
code, we suggest using InfluxQL.
|
||||
|
||||
As we developed InfluxDB v3, our top priority was improving performance at the
|
||||
database layer: faster ingestion, better compression, enhanced querying,
|
||||
and more scalability. However, this meant we couldn’t bring everything forward
|
||||
from v2. As InfluxDB v3 is a ground-up rewrite of the database in a new language
|
||||
(from Go to Rust), we couldn’t bring Flux forward to v3.
|
||||
|
||||
- [What do you mean by Flux is in maintenance mode?](#what-do-you-mean-by-flux-is-in-maintenance-mode)
|
||||
- [Is Flux going to End-of-Life?](#is-flux-going-to-end-of-life)
|
||||
- [What alternatives do you have for Flux Tasks?](#what-alternatives-do-you-have-for-flux-tasks)
|
||||
|
||||
## What do you mean by Flux is in maintenance mode?
|
||||
|
||||
We still support Flux, but are not actively developing any new Flux features.
|
||||
We will continue to provide security patches and will address any critical
|
||||
defects through the maintenance period.
|
||||
Our focus is our latest database engine, InfluxDB v3, and its associated products.
|
||||
|
||||
## Is Flux going to End-of-Life?
|
||||
|
||||
No, we will continue to support Flux for the foreseeable future.
|
||||
We will continue to support our customers who have invested in Flux and have
|
||||
built apps that use it. You can continue using Flux, but if you want to
|
||||
future-proof your code, we recommend using InfluxQL or SQL.
|
||||
|
||||
## What alternatives do you have for Flux tasks?
|
||||
|
||||
If moving to InfluxDB v3, you can't bring Flux tasks because InfluxDB v3 doesn't
|
||||
support Flux natively. When you move to v3, you will need to rewrite your tasks
|
||||
using whatever technologies your team prefers. However, if you’re using tasks
|
||||
for downsampling specifically, the storage performance in v3 is much better so
|
||||
you may no longer need tasks for this functionality.
|
||||
|
|
@ -21,8 +21,14 @@ date or through the Google Cloud Platform (GCP) or Azure marketplaces, see the
|
|||
To see which storage engine your organization is using,
|
||||
find the **InfluxDB Cloud powered by** link in your
|
||||
[InfluxDB Cloud organization homepage](https://cloud2.influxdata.com) version information.
|
||||
If your organization is using InfluxDB 3.0, you'll see
|
||||
If your organization is using InfluxDB v3, you'll see
|
||||
**InfluxDB Cloud Serverless** followed by the version number.
|
||||
|
||||
#### InfluxDB v3 and Flux
|
||||
|
||||
InfluxDB Cloud Serverless and other InfluxDB v3 products do not support Flux.
|
||||
Flux is now in maintenance mode. For more information, see
|
||||
[The future of Flux](/flux/v0/future-of-flux).
|
||||
{{% /note %}}
|
||||
|
||||
InfluxDB Cloud Serverless is a hosted and managed version of InfluxDB backed
|
||||
|
|
|
|||
|
|
@ -3,32 +3,38 @@
|
|||
# - id: unique ID for notification, cannot start with digit, no spaces, a-z and 0-9
|
||||
# level: note or warn
|
||||
# scope:
|
||||
# - list of URL paths to show notification on, no scope shows everywhere
|
||||
# - list of URL paths to show the notification on, no scope shows everywhere
|
||||
# exclude:
|
||||
# - list of URL paths to not show the notification on
|
||||
# title: Message title
|
||||
# slug: (optional) Short notification summary
|
||||
# message: |
|
||||
# Markdown message content.
|
||||
|
||||
- id: future-of-flux
|
||||
level: warn
|
||||
- id: future-of-flux-new
|
||||
level: note
|
||||
scope:
|
||||
- /flux/v0
|
||||
- /influxdb/v1
|
||||
- /influxdb/v2
|
||||
- /influxdb/cloud/
|
||||
- /influxdb/v1/flux/
|
||||
- /influxdb/v2/query-data/get-started/
|
||||
- /influxdb/cloud/query-data/get-started/
|
||||
exclude:
|
||||
- /flux/v0/future-of-flux/
|
||||
title: The future of Flux
|
||||
slug: |
|
||||
Flux is going into maintenance mode. You can continue using it as you
|
||||
currently are without any changes to your code.
|
||||
message: |
|
||||
Flux is going into maintenance mode and will not be supported in InfluxDB 3.0.
|
||||
This was a decision based on the broad demand for SQL and the continued growth
|
||||
and adoption of InfluxQL. We are continuing to support Flux for users in 1.x
|
||||
and 2.x so you can continue using it with no changes to your code.
|
||||
If you are interested in transitioning to InfluxDB 3.0 and want to
|
||||
future-proof your code, we suggest using InfluxQL.
|
||||
|
||||
For information about the future of Flux, see the following:
|
||||
[Read more](/flux/v0/future-of-flux)
|
||||
# message: |
|
||||
# Flux is going into maintenance mode and will not be supported in InfluxDB 3.0.
|
||||
# This was a decision based on the broad demand for SQL and the continued growth
|
||||
# and adoption of InfluxQL. We are continuing to support Flux for users in 1.x
|
||||
# and 2.x so you can continue using it with no changes to your code.
|
||||
# If you are interested in transitioning to InfluxDB 3.0 and want to
|
||||
# future-proof your code, we suggest using InfluxQL.
|
||||
|
||||
- [The plan for InfluxDB 3.0 Open Source](https://influxdata.com/blog/the-plan-for-influxdb-3-0-open-source)
|
||||
- [InfluxDB 3.0 benchmarks](https://influxdata.com/blog/influxdb-3-0-is-2.5x-45x-faster-compared-to-influxdb-open-source/)
|
||||
# For information about the future of Flux, see the following:
|
||||
|
||||
# - [The plan for InfluxDB 3.0 Open Source](https://influxdata.com/blog/the-plan-for-influxdb-3-0-open-source)
|
||||
# - [InfluxDB 3.0 benchmarks](https://influxdata.com/blog/influxdb-3-0-is-2.5x-45x-faster-compared-to-influxdb-open-source/)
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
<div id="docs-notifications">
|
||||
{{ range .Site.Data.notifications }}
|
||||
<div class="notification {{ .level }} min" id="{{ .id }}" data-scope='{{ if .scope }}{{ delimit .scope "," }}{{ else }}/{{ end }}'>
|
||||
<div class="notification {{ .level }} min" id="{{ .id }}" data-scope='{{ if .scope }}{{ delimit .scope "," }}{{ else }}/{{ end }}' data-exclude='{{ if .exclude }}{{ delimit .exclude ","}}{{ end }}'>
|
||||
<div class="close-notification"><span class="cf-icon Remove_New"></span></div>
|
||||
<div class="notification-title">
|
||||
<h3>{{ .title }}</h3>
|
||||
</div>
|
||||
|
|
@ -9,11 +10,12 @@
|
|||
{{ .slug | markdownify }}
|
||||
</div>
|
||||
{{ end }}
|
||||
{{ if .message }}
|
||||
<div class="notification-content">
|
||||
{{ .message | markdownify }}
|
||||
</div>
|
||||
<div class="close-notification"><span class="cf-icon Remove_New"></span></div>
|
||||
<span class="show"></span>
|
||||
{{ end }}
|
||||
</div>
|
||||
{{ end }}
|
||||
</div>
|
||||
|
|
|
|||
Loading…
Reference in New Issue