QOS.ch JIRA

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • logback-classic
  • LBCLASSIC-198

DBAppender: Support long event_id values in logging_event

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.9.18
  • Fix Version/s: None
  • Component/s: appender
  • Labels:
    None

Description

Want to retain longer history of logging events.
  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Java Source File
    DBAppender.java
    22/Mar/10 8:45 PM
    7 kB
    Michael Lynch
  2. Java Source File
    DBAppenderBase.java
    22/Mar/10 8:45 PM
    5 kB
    Michael Lynch

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • History
  • Activity
Hide
Permalink
Michael Lynch added a comment - 22/Mar/10 8:45 PM
Attached changes to core.db.DBAppenderBase and classic.db.DBAppender.
Show
Michael Lynch added a comment - 22/Mar/10 8:45 PM Attached changes to core.db.DBAppenderBase and classic.db.DBAppender.
Hide
Permalink
Ceki Gulcu added a comment - 22/Mar/10 8:51 PM
In java 'int' is 32 bits, ranging from approx -2Billion to 2billion. Why would you ever want 'long' (64bit) event_id values?
Show
Ceki Gulcu added a comment - 22/Mar/10 8:51 PM In java 'int' is 32 bits, ranging from approx -2Billion to 2billion. Why would you ever want 'long' (64bit) event_id values?
Hide
Permalink
Rü added a comment - 23/Mar/10 8:49 AM
Actually we produce on average about 1 GB of logs per day... for one application only! I haven't counted the actual log statements issued, but it's ~25 million lines. We don't throw any logs away, so it would not take too long for the 2 billion limit to be reached. And I don't think we are an absolute extreme, are we?
Show
Rü added a comment - 23/Mar/10 8:49 AM Actually we produce on average about 1 GB of logs per day... for one application only! I haven't counted the actual log statements issued, but it's ~25 million lines. We don't throw any logs away, so it would not take too long for the 2 billion limit to be reached. And I don't think we are an absolute extreme, are we?
Hide
Permalink
Joern Huxhorn added a comment - 23/Mar/10 9:30 AM
I'd also vote for 64bits here.

If something really big is logging (e.g. Google) than 2 billion isn't really unrealistic. I'd always go for 64bit ids, simply to stay on the safe side.
Show
Joern Huxhorn added a comment - 23/Mar/10 9:30 AM I'd also vote for 64bits here. If something really big is logging (e.g. Google) than 2 billion isn't really unrealistic. I'd always go for 64bit ids, simply to stay on the safe side.
Hide
Permalink
Ceki Gulcu added a comment - 24/Mar/10 12:09 AM
Fixed in a recent commit.
Show
Ceki Gulcu added a comment - 24/Mar/10 12:09 AM Fixed in a recent commit.

People

  • Assignee:
    Ceki Gulcu
    Reporter:
    Michael Lynch
Vote (0)
Watch (0)

Dates

  • Created:
    22/Mar/10 8:43 PM
    Updated:
    24/Mar/10 12:09 AM
    Resolved:
    24/Mar/10 12:09 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for logback. Try JIRA - bug tracking software for your team.