[
https://issues.apache.org/jira/browse/DRILL-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252672#comment-16252672
]
ASF GitHub Bot commented on DRILL-4286:
---------------------------------------
Github user dvjyothsna commented on a diff in the pull request:
https://github.com/apache/drill/pull/921#discussion_r150993718
--- Diff: exec/java-exec/src/main/resources/rest/index.ftl ---
@@ -57,19 +57,19 @@
<th>Control Port</th>
<th>Data Port</th>
<th>Version</th>
+ <th>Status</th>
</tr>
</thead>
<tbody>
<#assign i = 1>
<#list model.getDrillbits() as drillbit>
- <tr>
+ <tr id="row-${i}">
<td>${i}</td>
- <td>${drillbit.getAddress()}
- <#if drillbit.isCurrent()>
+ <td id="address" >${drillbit.getAddress()}<#if
drillbit.isCurrent()>
<span class="label label-info">Current</span>
</#if>
</td>
- <td>${drillbit.getUserPort()}</td>
+ <td id="port" >${drillbit.getUserPort()}</td>
--- End diff --
Yes, true. But for every row I have a different ID ("row-1") and I'm
accessing "port"(child) of that row. This was the entire row is unique and
need not assign a new unique id for every element in that row. Am I missing
something here?
> Have an ability to put server in quiescent mode of operation
> ------------------------------------------------------------
>
> Key: DRILL-4286
> URL: https://issues.apache.org/jira/browse/DRILL-4286
> Project: Apache Drill
> Issue Type: New Feature
> Components: Execution - Flow
> Reporter: Victoria Markman
> Assignee: Venkata Jyothsna Donapati
>
> I think drill will benefit from mode of operation that is called "quiescent"
> in some databases.
> From IBM Informix server documentation:
> {code}
> Change gracefully from online to quiescent mode
> Take the database server gracefully from online mode to quiescent mode to
> restrict access to the database server without interrupting current
> processing. After you perform this task, the database server sets a flag that
> prevents new sessions from gaining access to the database server. The current
> sessions are allowed to finish processing. After you initiate the mode
> change, it cannot be canceled. During the mode change from online to
> quiescent, the database server is considered to be in Shutdown mode.
> {code}
> This is different from shutdown, when processes are terminated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
