[IMPALA-4549] Validation of timestamp year is inconsistent about whether upper bound is 9999 or 10000

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 2.8.0
• Fix Version/s: Impala 2.9.0
• Component/s: Backend
• Assignee: Tim Armstrong
• Reporter: Tim Armstrong
• Created: 28/Nov/16 22:59
• Updated: 19/Jan/17 00:13
• Resolved: 19/Jan/17 00:13

Description

Boost is inconsistent in whether the maximum supported year is 9999 or 10000. This means that sometimes values with year=10000 get caught by validation and in other cases don't get caught. I think the severity is not high, since the exception-throwing validation uses the looser limit of 10000.

I filed a bug against boost: https://svn.boost.org/trac/boost/ticket/12630

Issue Links

• is related to: IMPALA-4498 Timestamp timezone conversion causes a crash