ForeverAngry
ForeverAngry
@the-other-tim-brown I was able to get the full stack trace printed out of the machine. I made most of the fields random names like "f1, f2 ... "except for the...
@the-other-tim-brown so, i rebuilt the table again, to make sure that there wasent something odd with the partitions. Its odd, the only change i made when rebuilding the table was...
@the-other-tim-brown Here it is, let me know if this wasnt what you were looking for! ``` { "format-version" : 2, "table-uuid" : "03e38c37-0ac5-4cae-a66f-49038931f265", "location" : "s3://", "last-sequence-number" : 114, "last-updated-ms"...
@the-other-tim-brown So the table had some null values in the timestamp. I got rid of those. Now im back to the original error i started with. The timestamps include the...
@the-other-tim-brown i re-pulled the main branch again, and rebuilt the Jar. _Note - i noticed that the run sync class changed from_ `io.onetable.utiliities.RunSync` to `org.apache.xtable.utilities.RunSync`, just an fyi - i...
@the-other-tim-brown Well, I feel a bit foolish - for some reason I thought you only wanted me to re pull and test the main branch. Sorry, I'll pull that branch...
@the-other-tim-brown Okay, i rebuilt the jar using the branch you provided, here is the stack trace: ``` Output: 2024-03-10 15:59:14 INFO io.onetable.utilities.RunSync:147 - Running sync for basePath s3:// for following...