You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "Caleb Meier (JIRA)" <ji...@apache.org> on 2017/02/28 18:07:45 UTC
[jira] [Resolved] (RYA-227) Extend RyaDetailToConfiguration to
handle invalid Fluo App Name and No Statistics Tables
[ https://issues.apache.org/jira/browse/RYA-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Caleb Meier resolved RYA-227.
-----------------------------
Resolution: Fixed
This has been resolved.
> Extend RyaDetailToConfiguration to handle invalid Fluo App Name and No Statistics Tables
> ----------------------------------------------------------------------------------------
>
> Key: RYA-227
> URL: https://issues.apache.org/jira/browse/RYA-227
> Project: Rya
> Issue Type: Bug
> Components: clients
> Affects Versions: 3.2.10
> Reporter: Caleb Meier
> Assignee: Caleb Meier
> Fix For: 3.2.10
>
>
> Currently the class RyaDetailsToConfiguration compares RyaDetails information with user specified configuration and adjusts the user's configuration so that it is consistent with the instance. Right now, only user indexer configuration flags are checked to see if they are consistent with the Rya Instance. There is currently no check to verify whether or not a user specified Fluo Updater Application is consistent with a Rya Instance and there is no check to make sure the cardinality and join selectivity tables exist if a user indicates that they want to use statistics. These checks need to put in place.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)