Known issues
The following are known issues in the Splunk Machine Learning Toolkit version 5.1.0.
Date filed | Issue number | Description |
---|---|---|
2023-02-21 | MLA-4451 | "Converting {} field(s) with categorical values into categorical fields" warning message should be logged discreetly and not appearing in UI/dashboard. Workaround: No workaround available. |
2020-03-10 | MLA-3871 | MLTK is using an unlimited number of cores |
2020-02-05 | MLA-3784 | Beta distribution results in negative alpha, beta values which causes DensityFunction to give Domain error in arguments |
2020-01-10 | MLA-3724 | Showcase: Card does not remain selected after user closes examples with X button |
2019-12-17 | MLA-3701 | Search bars in Assistants will not display more than approximately 500k rows Workaround: This is mostly a visual issue - the actual number of results the Assistant will use when fitting a model is not affected. |
2019-12-11 | MLA-3686 | MLTK Assistants do not support quote characters in field names Workaround: Use the "rename" or "eval" command to rename the field prior to using it. |
2019-10-09 | MLA-3559 | Loading settings from experiment history while in the Learn stage will lead to warnings, even when inputs are correct |
2019-08-30 | MLA-3423 | Add a warning message when kfold_cv is set to number greater than half of the datasize |
2019-07-12 | MLA-3237 | Anova table does not allow some special characters in formula so in field names also Workaround: Rename your field names before running "score anova" if they include one or more of those special characters: (r'[&%$#@!`\|";<>^]')
|
2019-03-28 | MLA-2965 | "Edit Job Settings" does not work in Assistants |
2018-09-24 | MLA-2547 | Experiments can't be renamed until they have been filled and saved Workaround: Load the Experiment, fill all necessary fields, and save it. You'll be able to rename the Experiment in the Save dialog. |
2018-06-12 | MLA-2258 | TFIDF returns a vague error message when the "token_pattern" parameter is invalid |
2018-04-18 | MLA-2147 | search.log does not show tracebacks on Windows on Splunk 7.1 Workaround: The user can still look at the logs on windows in mlspl.log which captures the traceback. However, many users may not have access to mlspl.log (as it is indexed in the _internal index which normal users don't have by default). If this is the case, they will need to ask their Splunk administrators for access to this index. |
2017-08-25 | MLA-1916 | Uncaught StatsModels error with ARIMA order=0-2-0 |
2017-02-28 | MLA-1670 | "Outliers Over Time" plot doesn't display any data if the _time field does not contain a Unix timestamp. |
2016-12-13 | MLA-1485 | In the Forecast Time Series assistant, forecasting a very large number of points may cause the browser to crash. |
What's new | Fixed issues |
This documentation applies to the following versions of Splunk® Machine Learning Toolkit: 5.1.0
Feedback submitted, thanks!