You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Hans Zeller (JIRA)" <ji...@apache.org> on 2016/05/20 01:20:16 UTC
[jira] [Updated] (TRAFODION-1175) LP Bug: 1444228 - Trafodion
should record the FQDN as client_name in Repository tables
[ https://issues.apache.org/jira/browse/TRAFODION-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hans Zeller updated TRAFODION-1175:
-----------------------------------
Fix Version/s: (was: 2.0-incubating)
2.1-incubating
> LP Bug: 1444228 - Trafodion should record the FQDN as client_name in Repository tables
> --------------------------------------------------------------------------------------
>
> Key: TRAFODION-1175
> URL: https://issues.apache.org/jira/browse/TRAFODION-1175
> Project: Apache Trafodion
> Issue Type: Bug
> Components: client-odbc-linux, connectivity-general
> Reporter: Chengxin Cai
> Assignee: Gao Jie
> Fix For: 2.1-incubating
>
>
> select distinct application_name, rtrim(client_name) from "_REPOS_".METRIC_QUERY_AGGR_TABLE;
> APPLICATION_NAME (EXPR)
> ---------------------------------------------------------- ----------------------------------------------------------------------------------------
> /usr/bin/python sq1176
> TrafCI sq1176.houston.hp.com
> --- 2 row(s) selected.
> Actually, sq1176 and sq1176.houston.hp.com are the same client, but they show different result when using odbc or jdbc client.
> They should always be the FQDN whatever the client is.
> And the same problem in METRIC_QUERY_TABLE and METRIC_SESSION_TABLE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)