You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2014/05/01 08:17:16 UTC

[jira] [Closed] (NUTCH-1497) Better default gora-sql-mapping.xml with larger field sizes for MySQL

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

Lewis John McGibbney closed NUTCH-1497.
---------------------------------------


> 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
>             Fix For: 2.3
>
>         Attachments: gora-mysql-mapping-patch, gora-mysql-mapping.xml, 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 was sent by Atlassian JIRA
(v6.2#6252)