[ 
https://issues.apache.org/jira/browse/CONNECTORS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174752#comment-13174752
 ] 

Karl Wright commented on CONNECTORS-334:
----------------------------------------

Checked in a number of changes across the board.  Most notable is that the 
MySQL JDBC driver's maxCharLength field is completely bogus and returns values 
that are essentially random.  We *were* using this field generally to insure 
that returned values did not exceed their schema length, but I'm going to have 
to discontinue use (or conditionalize it) in order to support MySQL.

Once all that was done, the tests are still failing because the crawl still 
hangs.  Reason is unclear.  The basic problem now is that when a document is in 
the "pending" state and the job is "active" we still don't get any processing 
activity.  There are no exceptions - just no documents.  The stuffer query must 
therefore be acting differently on MySQL than on every other database.

This has been the hardest database port we've yet attempted for ManifoldCF.  
MySQL is incredibly idiosyncratic and appears to do many things in a manner 
wholly its own.  It may therefore be quite some time before this all works.

                
> Make ManifoldCF fully run on MySQL
> ----------------------------------
>
>                 Key: CONNECTORS-334
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-334
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Framework core
>    Affects Versions: ManifoldCF 0.5
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.5
>
>
> Make ManifoldCF run properly on top of MySQL.  The ticket should be viewed as 
> a combination of the MySQL contributions from CONNECTORS-314, plus tests and 
> other changes needed to make MySQL be a viable option for crawling.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to