[
https://issues.apache.org/jira/browse/NUTCH-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736717#action_12736717
]
Andrzej Bialecki commented on NUTCH-650:
-----------------------------------------
We already have some compat stuff in o.a.n.util.compat, mostly related to 0.7
and early 0.8 conversion. I guess we can drop this stuff from the new branch.
This is a bigger question of back-compat. What data is it worth to convert and
preserve? I'd say the following: CrawlDb and perhaps unparsed content.
Everything else can be generated from this data.
With such major changes I'm in favor of a limited back-compat based on
converter tools, and not on back-compat shims scattered throughout the code. So
feel free to morph the core classes as you see fit according to the
requirements of the new design.
And answering your question: no objections here.
> Hbase Integration
> -----------------
>
> Key: NUTCH-650
> URL: https://issues.apache.org/jira/browse/NUTCH-650
> Project: Nutch
> Issue Type: New Feature
> Affects Versions: 1.0.0
> Reporter: Doğacan Güney
> Assignee: Doğacan Güney
> Fix For: 1.1
>
> Attachments: hbase-integration_v1.patch, hbase_v2.patch,
> malformedurl.patch, meta.patch, meta2.patch, nofollow-hbase.patch,
> nutch-habase.patch, searching.diff, slash.patch
>
>
> This issue will track nutch/hbase integration
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
