Known and resolved issues
This topic lists known and resolved issues for Hunk functionality. For a full list of issues, see the Splunk 6.1 Known Issues.
Known Issues
- In 6.1, you cannot configure Hunk to run reports as a different user. Instead, use the new pass-through authentication functionality to run users with the Hunk Superuser acting as a proxy. See About pass-through authentication for more information. (ERP-709)
- Unable to edit provider names that contain special characters. To mitigate this, avoid using special characters when naming new providers. (ERP-672)
Resolved issues
Note that in addition to resolved issues for Hunk, 6.1.1 also provides important fixes that are related to underlying Splunk functionality. See the Splunk 6.1.1 changelog for the full list.
- The Cloudera tarball (v4.5 and higher) comes with two bin directories, each for YARN (default) and MapReduce1, when specifying HADOOP_HOME in Hunk however "bin" is implicit. If you are running MapReduce1 using the Cloudera tarball v4.5 or higher, when you untar the Hadoop libraries from
http://archive.cloudera.com/cdh4/cdh/4/hadoop-2.0.0-cdh4.5.0.tar.gz
or higher you should rename these folders as follows:- rename
bin
tobin-yarn
- rename
bin-mapreduce1
tobin
(ERP-575)
- rename
PREVIOUS Manage report acceleration |
NEXT Troubleshoot Hunk |
This documentation applies to the following versions of Hunk®(Legacy): 6.1.1
Feedback submitted, thanks!