[
https://issues.apache.org/jira/browse/HIVE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654869#action_12654869
]
Johan Oskarsson commented on HIVE-144:
--------------------------------------
Personally I would avoid preprocessing altogether, it sounds like a messy path
to go down. For example unit testing becomes a pain and new code might have to
be developed in two versions. And for example the unit testing template code is
impossible to edit with an IDE.
It seems the reason behind using the preprocessor is to support multiple Hadoop
versions? Would it not be simpler and easier for both developers and the end
user if for example Hive 0.19 only worked with Hadoop 0.19? That way there
wouldn't be a need for preprocessed code. This is how HBase does it.
Are there any major drawbacks of that solution?
> Ql java source copied to build/gen-java
> ---------------------------------------
>
> Key: HIVE-144
> URL: https://issues.apache.org/jira/browse/HIVE-144
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Affects Versions: 0.19.0
> Reporter: Johan Oskarsson
> Priority: Trivial
> Fix For: 0.19.0
>
>
> Since HIVE-98, the build process copies the contents of the ql/src/java
> directory to build/gen-java where the code generated from Hive.g is located.
> This makes it a bit more difficult to work on the project in Eclipse, since
> one has to add the build/gen-java folder to the project and not ql/src/java.
> This means we'll edit the ql java files in the wrong location. Adding both of
> these directories will of course result in duplicate entries.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
