Skip to content

Commit 0d7f6cf

Browse files
committed
address comments
1 parent f7c93ae commit 0d7f6cf

File tree

1 file changed

+8
-27
lines changed

1 file changed

+8
-27
lines changed

dev/run-tests

Lines changed: 8 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -133,51 +133,32 @@ CURRENT_BLOCK=$BLOCK_PYTHON_STYLE
133133

134134
echo ""
135135
echo "========================================================================="
136-
echo "Building Spark with hive 0.12"
136+
echo "Building Spark"
137137
echo "========================================================================="
138138

139139
CURRENT_BLOCK=$BLOCK_BUILD
140140

141141
{
142142
# We always build with Hive because the PySpark Spark SQL tests need it.
143-
BUILD_MVN_PROFILE_ARGS_12="$SBT_MAVEN_PROFILES_ARGS -Phive -Phive-0.12.0"
143+
BUILD_MVN_PROFILE_ARGS="$SBT_MAVEN_PROFILES_ARGS -Phive -Phive-0.12.0"
144144

145-
echo "[info] Building Spark with these arguments: $BUILD_MVN_PROFILE_ARGS_12"
145+
echo "[info] Building Spark with these arguments: $BUILD_MVN_PROFILE_ARGS"
146146

147147
# NOTE: echo "q" is needed because sbt on encountering a build file with failure
148148
#+ (either resolution or compilation) prompts the user for input either q, r, etc
149149
#+ to quit or retry. This echo is there to make it not block.
150-
# NOTE: Do not quote $BUILD_MVN_PROFILE_ARGS_12 or else it will be interpreted as a
150+
# NOTE: Do not quote $BUILD_MVN_PROFILE_ARGS or else it will be interpreted as a
151151
#+ single argument!
152152
# QUESTION: Why doesn't 'yes "q"' work?
153153
# QUESTION: Why doesn't 'grep -v -e "^\[info\] Resolving"' work?
154+
# First build with 0.12 to ensure patches do not break the hive 12 build
154155
echo -e "q\n" \
155-
| sbt/sbt $BUILD_MVN_PROFILE_ARGS_12 clean package assembly/assembly \
156+
| sbt/sbt $BUILD_MVN_PROFILE_ARGS clean hive/compile hive-thiftserver/compile \
156157
| grep -v -e "info.*Resolving" -e "warn.*Merging" -e "info.*Including"
157-
}
158-
159-
echo ""
160-
echo "========================================================================="
161-
echo "Building Spark with hive 0.13"
162-
echo "========================================================================="
163158

164-
CURRENT_BLOCK=$BLOCK_BUILD
165-
166-
{
167-
# We always build with Hive because the PySpark Spark SQL tests need it.
168-
BUILD_MVN_PROFILE_ARGS_13="$SBT_MAVEN_PROFILES_ARGS -Phive -Phive-0.13.1"
169-
170-
echo "[info] Building Spark with these arguments: $BUILD_MVN_PROFILE_ARGS_13"
171-
172-
# NOTE: echo "q" is needed because sbt on encountering a build file with failure
173-
#+ (either resolution or compilation) prompts the user for input either q, r, etc
174-
#+ to quit or retry. This echo is there to make it not block.
175-
# NOTE: Do not quote $BUILD_MVN_PROFILE_ARGS_13 or else it will be interpreted as a
176-
#+ single argument!
177-
# QUESTION: Why doesn't 'yes "q"' work?
178-
# QUESTION: Why doesn't 'grep -v -e "^\[info\] Resolving"' work?
159+
# Then build with default version(0.13.1) because tests based on this version
179160
echo -e "q\n" \
180-
| sbt/sbt $BUILD_MVN_PROFILE_ARGS_13 clean package assembly/assembly \
161+
| sbt/sbt $SBT_MAVEN_PROFILES_ARGS -Phive clean hive/compile hive-thiftserver/compile \
181162
| grep -v -e "info.*Resolving" -e "warn.*Merging" -e "info.*Including"
182163
}
183164

0 commit comments

Comments
 (0)