You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/05/30 17:21:03 UTC
[jira] [Resolved] (BIGTOP-1270) BigPetStore: Productionize the Hive
portion
[ https://issues.apache.org/jira/browse/BIGTOP-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jay vyas resolved BIGTOP-1270.
------------------------------
Resolution: Won't Fix
pending no comments on HIVE-7115 and no other opinions im closing this jira, and we can ignore hive for now in bigpetstore, until someone comes up with a good way to integration test it locally in our java builds. See BIGTOP-1271 for details on how we will feed data into mahout, without using hive to create hash codes.
> BigPetStore: Productionize the Hive portion
> -------------------------------------------
>
> Key: BIGTOP-1270
> URL: https://issues.apache.org/jira/browse/BIGTOP-1270
> Project: Bigtop
> Issue Type: New Feature
> Components: Blueprints
> Affects Versions: backlog
> Reporter: jay vyas
>
> The hive portion of the BigPetStore blueprint app builds a "view" over the cleaned data that Mahout can then use to do product recommendations.
> The hive code in bigpetstore only runs locally - lets add the necessary configuration hooks and/or (if we have to) externalize the hive script itself from java so that its easy to run directly on a cluster.
> And lets actually run it on some kind of a cluster at scale. The contract for the hive portion is an output file with three numbers like this:
> {noformat}
> 100 30021 1
> 100 212341 1
> ...
> {noformat}
> Signifying that customer=100 likes both of the products "30021" and "212341".
--
This message was sent by Atlassian JIRA
(v6.2#6252)