Re: Exception refactoring proposal

:-) Makes sense. On 1/6/17 3:27 PM, Till Westmann wrote: Hi, I like the proposal and I’d like to propose on more change: Let’s not start the names of ErrorCodes with "ERROR_". In the code they are usually used as ErrorCode.ERROR_THIS_IS_THE_PROBLEM and it seems that

Re: Exception refactoring proposal

All right, sounds good! Best, Yingyi On Fri, Jan 6, 2017 at 3:36 PM, Till Westmann wrote: > Yes, that’s what I would think as well. > > Cheers, > Till > > On 6 Jan 2017, at 15:30, Yingyi Bu wrote: > > > Sounds good to me. > > I'm guessing that eventually WARNINGs will also

Re: Exception refactoring proposal

Yes, that’s what I would think as well. Cheers, Till On 6 Jan 2017, at 15:30, Yingyi Bu wrote: > Sounds good to me. > I'm guessing that eventually WARNINGs will also have WaringCode.java? > (Although we currently don't have WARNING channels...) > > Best, > Yingyi > > On Fri, Jan 6, 2017 at 3:27

Re: Exception refactoring proposal

+1 Best, Taewoo On Fri, Jan 6, 2017 at 3:27 PM, Till Westmann wrote: > Hi, > > I like the proposal and I’d like to propose on more change: > Let’s not start the names of ErrorCodes with "ERROR_". > In the code they are usually used as > >

Writing to and Reading from Metadata Pages

Glorious dev, Recently, we changed the way we write to and read from Metadata pages. Previously, we had specific methods to write fixed sized specific information to metadata pages. For example: public void setLSN(long lsn); public long getLSN(); public void setLSMComponentFilterPageId(int

Jenkins build is back to stable : asterix-integration-tests d49bc6eb

See

Jenkins build is still unstable: asterix-integration-tests 0aeebae0

See