manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CONNECTORS-110) Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB
Date Tue, 13 Jan 2015 08:56:34 GMT

     [ https://issues.apache.org/jira/browse/CONNECTORS-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Wright resolved CONNECTORS-110.
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: ManifoldCF next)
                   ManifoldCF 1.2

Was fixed long ago, just need a reasonable fix-in field

> Max activity and Max bandwidth reports don't work properly under Derby or HSQLDB
> --------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-110
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-110
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework crawler agent
>    Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.2
>
>
> The reason for the failure is because the queries used are doing the Postgresql DISTINCT
ON (xxx) syntax, which Derby does not support.  Unfortunately, there does not seem to be a
way in Derby at present to do anything similar to DISTINCT ON (xxx), and the queries really
can't be done without that.
> One option is to introduce a getCapabilities() method into the database implementation,
which would allow ACF to query the database capabilities before even presenting the report
in the navigation menu in the UI.  Another alternative is to do a sizable chunk of resultset
processing within ACF, which would require not only the DISTINCT ON() implementation, but
also the enclosing sort and limit stuff.  It's the latter that would be most challenging,
because of the difficulties with i18n etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message