Compile alone did not show the scala code changes AFAICT. I will reverify. 2015-03-27 10:16 GMT-07:00 Davies Liu <dav...@databricks.com>:
> I usually just open a terminal to do `build/sbt ~compile`, coding in > IntelliJ, then run python tests in another terminal once it compiled > successfully. > > On Fri, Mar 27, 2015 at 10:11 AM, Reynold Xin <r...@databricks.com> wrote: > > Python is tough if you need to change Scala at the same time. > > > > sbt/sbt assembly/assembly > > > > can be slightly faster than just assembly. > > > > > > On Fri, Mar 27, 2015 at 10:02 AM, Stephen Boesch <java...@gmail.com> > wrote: > > > >> I am iteratively making changes to the scala side of some new pyspark > code > >> and re-testing from the python/pyspark side. > >> > >> Presently my only solution is to rebuild completely > >> > >> sbt assembly > >> > >> after any scala side change - no matter how small. > >> > >> Any better / expedited way for pyspark to see small scala side updates? > >> >
