[
https://issues.apache.org/jira/browse/NUTCH-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495272#comment-13495272
]
Nathan Gass commented on NUTCH-1497:
------------------------------------
It seems to me that gora should hide as many database specifics as possible,
and gora actually seems to do this just fine in this cases (using mysql
specific column types when length is large). What are the disadvantages with
hsqldb using the new length values?
> Better default gora-sql-mapping.xml with larger field sizes for MySQL
> ---------------------------------------------------------------------
>
> Key: NUTCH-1497
> URL: https://issues.apache.org/jira/browse/NUTCH-1497
> Project: Nutch
> Issue Type: Improvement
> Components: storage
> Affects Versions: 2.2
> Environment: MySQL Backend
> Reporter: James Sullivan
> Priority: Minor
> Labels: MySQL
> Attachments: gora-mysql-mapping.xml
>
>
> The current generic default gora-sql-mapping.xml has field sizes that are too
> small in almost all situations when used with MySQL. I have included a
> mapping which will work better for MySQL (takes slightly more space but will
> be able to handle larger fields necessary for real world use). Includes patch
> from Nutch-1490 and resolves the non-Unicode part of Nutch-1473. I believe it
> is not possible to use the same gora-sql-mapping for both hsqldb and MySQL
> without a significantly degraded lowest common denominator resulting. Should
> the user manually rename the attached file to gora-sql-mapping.xml or is
> there a way to have Nutch automatically use it when MySQL is selected in
> other configurations (Ivy.xml or gora.properties)?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
