[
https://issues.apache.org/jira/browse/TRAFODION-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15771661#comment-15771661
]
ASF GitHub Bot commented on TRAFODION-2417:
-------------------------------------------
Github user mkby commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/888#discussion_r93724802
--- Diff: core/sqf/sqenvcom.sh ---
@@ -139,6 +139,10 @@ else
fi
export TRAF_HOME=$PWD
+# normal installed location, can be overridden in .trafodion
+export DCS_INSTALL_DIR=$TRAF_HOME/dcs-$TRAFODION_VER
+export REST_INSTALL_DIR=$TRAF_HOME/rest-$TRAFODION_VER
+
--- End diff --
I like this idea, but where does `$TRAFODION_VER` variable come from?
> Pre-work for ambari integration
> -------------------------------
>
> Key: TRAFODION-2417
> URL: https://issues.apache.org/jira/browse/TRAFODION-2417
> Project: Apache Trafodion
> Issue Type: Sub-task
> Components: installer
> Reporter: Steve Varnau
>
> Some install operations done in the command line installers (bash/python) can
> be done as part of RPM install. Particularly, system limits config & sudo
> config for trafodion user. These are not dependent on cluster configuration.
> Secondly, the command-line installers modify the trafci script at install
> time. This can be re-factored so that we just modify a config file rather
> than modify the script itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
