oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OODT-460) DataSourceCatalog doesn't work with MySQL
Date Sat, 15 Jul 2017 06:00:01 GMT

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

Chris A. Mattmann resolved OODT-460.
    Resolution: Won't Fix

not enough time

> DataSourceCatalog doesn't work with MySQL
> -----------------------------------------
>                 Key: OODT-460
>                 URL: https://issues.apache.org/jira/browse/OODT-460
>             Project: OODT
>          Issue Type: Bug
>          Components: file manager
>    Affects Versions: 0.3
>         Environment: none
>            Reporter: Brian Foster
>            Assignee: Tom Barber
>             Fix For: 1.1
> It appears when support was added for BooleanQueries we lost support with MySQL.
> Either a INTERSECT substitute which is supported across the board can be used or maybe
just turn DataSourceCatalog into OracleDataSourceCatalog and then create a MySqlDataSourceCatalog
(this way each can be further customized to use custom statements for each to gain speed improvements)...
then possible find some happy medium command for INTERSECT and have DataSourceCatalog use
that -- in other words, this issue will split DataSourceCatalog into 3 classes:
> DataSourceCatalog : generic data source catalog (not neccessarily fast or pretty, but
works for all SQL DBs)
> OracleDataSourceCatalog : customized for speed and use with Oracle specifically
> MySqlDataSourceCatalog : customized for speed and use with MySQL specifically 

This message was sent by Atlassian JIRA

View raw message