Known and resolved issues
This topic lists known and resolved issues for Hunk functionality. For a full list of issues, see the Splunk Enterprise 6.2 Known Issues.
Known Issues
- Report acceleration summary gets deleted when two Hunk instances point to the same Splunk working directory. To mitigate this issue, make sure that
vix.splunk.home.hdfs
(or Working directory in the UI) is unique on both search heads that are not in a pool. To keep keep your instances in the same working directory, you configure vix.splunk.search.cache.path to be unique on both search heads. (ERP-1164)
- Data Explorer preview does not honor existing sourcetypes for big5/sjis files. (ERP-1216)
Resolved issues
The following issues have been resolved in this release:
- 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)
Deprecated features
The ability to configure Hunk to run reports as a different user has been deprecated. Instead we recommend that you use pass-through authentication.
PREVIOUS Manage report acceleration |
NEXT Troubleshoot Hunk |
This documentation applies to the following versions of Hunk®(Legacy): 6.2
Feedback submitted, thanks!