Return-Path: <dev-return-32707-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 119E7200B65
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed,  3 Aug 2016 01:37:23 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 10503160AA8; Tue,  2 Aug 2016 23:37:23 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 2A7C4160AAC
	for <archive-asf-public@cust-asf.ponee.io>; Wed,  3 Aug 2016 01:37:22 +0200 (CEST)
Received: (qmail 7055 invoked by uid 500); 2 Aug 2016 23:37:21 -0000
Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@phoenix.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@phoenix.apache.org>
List-Post: <mailto:dev@phoenix.apache.org>
List-Id: <dev.phoenix.apache.org>
Reply-To: dev@phoenix.apache.org
Delivered-To: mailing list dev@phoenix.apache.org
Received: (qmail 6689 invoked by uid 99); 2 Aug 2016 23:37:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2016 23:37:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id CDC322C0D67
	for <dev@phoenix.apache.org>; Tue,  2 Aug 2016 23:37:20 +0000 (UTC)
Date: Tue, 2 Aug 2016 23:37:20 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.12994403.1470175281000.205807.1470181040839@Atlassian.JIRA>
In-Reply-To: <JIRA.12994403.1470175281000@Atlassian.JIRA>
References: <JIRA.12994403.1470175281000@Atlassian.JIRA> <JIRA.12994403.1470175281171@arcas>
Subject: [jira] [Resolved] (PHOENIX-3139) phoenix-hive assembly target
 failure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Tue, 02 Aug 2016 23:37:23 -0000


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

Andrew Purtell resolved PHOENIX-3139.
-------------------------------------
    Resolution: Not A Problem

Yes {{clean install package}} was the problem. Just a {{clean package}} works fine. This is a new wrinkle for the Phoenix build though introduced by the new phoenix-hive module. 

> phoenix-hive assembly target failure
> ------------------------------------
>
>                 Key: PHOENIX-3139
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3139
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.8.0
>            Reporter: Andrew Purtell
>            Priority: Minor
>
> There is a maven-assembly-plugin target in the phoenix-hive module POM not present in other extension module POMs like for phoenix-pig or phoenix-flume.
> This assembly target creates a jar-with-dependencies assembly as phoenix-hive/target/phoenix-<version>-hive.jar. I think that path is also an implicit input to the assembly as the output of the earlier compile phase. I say that because I see the build failing with an odd error:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.5.2:single
> (make-jar-with-dependencies) on project phoenix-hive:
> Failed to create assembly:
> Error creating assembly archive jar-with-dependencies:
> Problem creating jar:
> jar:file:/.../phoenix-hive/target/phoenix-hive-<version>.jar!/org/apache/phoenix/hive/mapreduce/PhoenixRecordWriter.class:
> JAR entry org/apache/phoenix/hive/mapreduce/PhoenixRecordWriter.class not found in /.../phoenix-hive/target/phoenix-hive-<version>.jar -
> {noformat}
> Makes sense that the archiver can't find a class file in a jar if a writer is racing with a reader on the same file.
> What was the intent here? Commenting out the maven-assembly-plugin instructions in the phoenix-hive POM fixes (or at least avoids) this problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)