panbingkun
panbingkun
> Nope, actually splitting the build increases the usage of the resource so I asked to distribute existing test cases for now. We got a bit of pushes from ASF...
> we now have limited resources. See also https://issues.apache.org/jira/browse/SPARK-48094 Okay, I see, thanks.
- In `Unify v1 and v2 ALTER TABLE .. UNSET TBLPROPERTIES tests` migration, I found syntax: ``` ALTER TABLE ... UNSET TBLPROPERTIES IF EXISTS ('key1'); ``` v1: ``` If the...
Okay, let me update it.
@cloud-fan It's ready now, thanks.
cc @LuciferYang @dongjoon-hyun @HyukjinKwon
> > maven-javadoc-plugin > > Can we check if the Scaladoc/Javadoc generation work fine? IIRC, genjavadoc is pretty old, and we should see if that's compatible with javadoc plugin upgrade...
> Without this PR, I tried to run `mvn javadoc:javadoc` and `mvn javadoc:jar` on `master/branch-3.5/branch-3.4`, and they both failed. I think we can initiate the upgrade of `maven-javadoc-plugin` after fixing...
> hmm... IIRC, https://github.com/panbingkun/spark/actions/runs/9458329785/artifacts/1587905559 is generated by `sbt unidoc`, it should not have used `maven-javadoc-plugin` Yes, that's right. I tested a PR (https://github.com/apache/spark/pull/46922) that completely removed `javadoc`, and `GA` seems...
> Gentle ping. What is the current status of this PR, @panbingkun ? I will update in the next few days. Thanks!