This is an automated email from the ASF dual-hosted git repository.
tbonelee pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/zeppelin.git
The following commit(s) were added to refs/heads/master by this push:
new aad361148c [ZEPPELIN-6497] Refresh stale Cassandra interpreter
embedded help links
aad361148c is described below
commit aad361148cdab6348c47f187909f88f30a83dd41
Author: Minho Jang <[email protected]>
AuthorDate: Mon Jul 20 23:27:32 2026 +0900
[ZEPPELIN-6497] Refresh stale Cassandra interpreter embedded help links
### What is this PR for?
The Cassandra interpreter help menu was linked to old Zeppelin
`0.6.0-SNAPSHOT` documentation pages for dynamic forms and interpreter binding
mode. Those links used outdated paths and HTTP URLs, which could send users to
stale documentation.
This PR updates those embedded help links to the current Zeppelin
documentation URLs under `https://zeppelin.apache.org/docs/latest/usage/...`.
### What type of PR is it?
Documentation
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-6497
### How should this be tested?
* Search for stale links:
```
rg -n "0\.6\.0-SNAPSHOT|manual/dynamicform|manual/interpreters"
cassandra/src/main/resources/scalate/helpMenu.ssp
```
### Questions:
* Does the license files need to update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
Closes #5324 from miinhho/docs/refresh-stale-cassandra-help-link.
Signed-off-by: ChanHo Lee <[email protected]>
---
cassandra/src/main/resources/scalate/helpMenu.ssp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/cassandra/src/main/resources/scalate/helpMenu.ssp
b/cassandra/src/main/resources/scalate/helpMenu.ssp
index 80fc99413a..7139cb512d 100644
--- a/cassandra/src/main/resources/scalate/helpMenu.ssp
+++ b/cassandra/src/main/resources/scalate/helpMenu.ssp
@@ -834,7 +834,7 @@ select id, double, float, text, date, time, timestamp from
zep.test_format;</pre
<div class="panel-body">
<p>
Instead of hard-coding your CQL queries, it is
possible to use <strong>
- <a
href="http://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/manual/dynamicform.html";
target="_blank" rel="noopener noreferrer">Zeppelin dynamic form</a>
+ <a
href="https://zeppelin.apache.org/docs/latest/usage/dynamic_form/intro.html";
target="_blank" rel="noopener noreferrer">Zeppelin dynamic form</a>
</strong> syntax to inject simple value or multiple
choices forms.
The legacy mustache syntax ( <strong>{{ }}</strong> )
to bind input text and select form is still supported but is deprecated and
will be removed in future releases.
@@ -1050,7 +1050,7 @@ select id, double, float, text, date, time, timestamp
from zep.test_format;</pre
It is possible to execute many paragraphs in parallel. However,
at the back-end side, we’re still using synchronous queries. <em>Asynchronous
execution</em> is only possible when it is possible to return a
<strong>Future</strong> value in the <strong>InterpreterResult</strong>. It may
be an interesting proposal for the <strong>Zeppelin</strong> project.
<br/><br/>
Recently, <strong>Zeppelin</strong> allows you to choose the
level of isolation for your interpreters (see
- <strong><a
href="http://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/manual/interpreters.html";
target="_blank" rel="noopener noreferrer">Interpreter Binding Mode</a></strong>
).
+ <strong><a
href="https://zeppelin.apache.org/docs/latest/usage/interpreter/interpreter_binding_mode.html";
target="_blank" rel="noopener noreferrer">Interpreter Binding
Mode</a></strong> ).
<br/><br/>
Long story short, you have 3 available bindings:
