[
https://issues.apache.org/jira/browse/PIO-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850749#comment-15850749
]
Pat Ferrel commented on PIO-45:
-------------------------------
You can use the UR from here;
https://github.com/actionml/universal-recommender, just uncomment the line the
disables the SelfCleaningDatasource. For property tests you can dump the App
data or look at the model in Elasticsearch.
The $set properties should never change with this input no matter what the
setting in the eventWindow. When Compression is enabled, only one $set is left
in the exported App data but it often has the wrong aggregated values as
described above. This translates to changing properties in the model with
compression vs without.
I used the latest develop version of PIO.
> SelfCleaningDatasource erases all data
> --------------------------------------
>
> Key: PIO-45
> URL: https://issues.apache.org/jira/browse/PIO-45
> Project: PredictionIO
> Issue Type: Bug
> Affects Versions: 0.10.0-incubating
> Reporter: Pat Ferrel
> Assignee: Alexander Merritt
> Priority: Blocker
> Fix For: 0.11.0
>
> Attachments: import_handmade_simple.py,
> sample-time-window-and-downsample-data.txt
>
>
> as integrated into the UR, in the integration-test, the SelfCleaningDataset
> erases all data. This feature works fine in the AML version of PIO.
> Although not tested one could assume that this would be true with any other
> Datasource in other templates.
> [~emergentorder] can you check to see if the PIO merge was done correctly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
