Does any see the following exception with the query against upsert table? I do not see the problem with offline table.

Caused by: java.lang.IllegalArgumentException: The datetime zone id 'America/Los_Angeles' is not recognised
        at org.joda.time.DateTimeZone.forID(DateTimeZone.java:247) ~[pinot-all-0.8.0-jar-with-dependencies.jar:0.8.0-d53965c35d75bff2fbe92706129cac9ca563aac3]
        at org.apache.pinot.common.function.scalar.DateTimeFunctions.year(DateTimeFunctions.java:335) ~[pinot-all-0.8.0-jar-with-dependencies.jar:0.8.0-d53965c35d75bff2fbe92706129cac9ca563aac3]
        at jdk.internal.reflect.GeneratedMethodAccessor1636.invoke(Unknown Source) ~[?:?]
        at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
        at org.apache.pinot.common.function.FunctionInvoker.invoke(FunctionInvoker.java:128) ~[pinot-all-0.8.0-jar-with-dependencies.jar:0.8.0-d53965c35d75bff2fbe92706129cac9ca563aac3]
        ... 19 more

could you share an example query?

Thanks a lot for your help! @Xiaobing The problem is that the pinot server is in bad state

Restarting the servers seem to help, could this be an issue with joda library having an issue initializing? Anyone else see this error?

thanks for sharing the issue. any clues to help reproduce this issue?

At this point just those log messages in the server and the fact that restarting clears those errors. We will continue to monitor and if we have any more info we'll share it

I haven’t seen

Strange too - most of the stack overflow or other searches report that it's due to an older version of joda, but Pinot uses a recent version...

yeah, I just spotted

pinot-all-0.8.0

in the log msg above. but found that 0.8.0 release used the same joda lib as seen on the current master branch of Pinot.

<dependency>
        <groupId>joda-time</groupId>
        <artifactId>joda-time</artifactId>
        <version>2.10.5</version>
      </dependency>

@Xiaobing did you see any weird issue resolved by restarting pinot server?

hmm.. not really to my own experience.