Known and resolved issues

Version 6.3.2

This topic lists known issues for Hunk functionality. For a full list of issues, see the Splunk Enterprise 6.3.2 Known Issues.

Known Issues

Publication date	Defect number	Description
2015-9-22	ERP-1650	Hunk does not properly deserialize timestamp data type.
2015-9-22	ERP-1619	archivebuckets force=1 and then rerun the search.
2015-9-22	ERP-1598	minsplit rampup - splits generation takes too long. To resolve this, set minsplits=maxsplits
2015-9-22	ERP-1595	Ramp up logic for minsplits/maxsplits does not works as expected for some values >100.
2015-9-22	ERP-1576	Report acceleration does not work with smart search index.
2015-9-22	ERP-1502	Non-accelerated pivot search on Pivot UI page waits for a long time to return result.
2015-9-22	ERP-1343	Hunk searches fail on corrupted journal.gz files, although Splunk searches run without error. Workaround is to add that journal.gz to the input path's blacklist (vix.input.1.ignore = ....)
2015-9-22		Required field optimization causes problems with time extraction. With structured data sets (such as csv, avro, parquet etc) Hunk tries to honor the list of required fields as passed down by the search. This may causes issues with _time.
2015-9-22	ERP-1164	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.
2015-9-22	ERP-1216	Data Explorer preview does not honor existing sourcetypes for big5/sjis files.

Resolved Issues

There are no Hunk-specific resolved issues. For related Splunk issues, see the Splunk Enterprise 6.3.2 changelog.