Derby
  1. Derby
  2. DERBY-2676

Class name "com.ibm.db2j.aggregates.Aggregator" refered in error message is no longer correct

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.6.1.0
    • Component/s: Documentation, SQL
    • Labels:
      None

      Description

      Error message for 42Y32 refers com.ibm.db2j.aggregates.Aggregator is as next.

      > 42Y32 Aggregator class '<className>' for aggregate '<aggregateName>' on
      > type <type> does not implement com.ibm.db2j.aggregates.Aggregator.

      Reading org.apache.derby.impl.sql.compile.AggregateNode#checkAggregatorClassName, however, the current fully qualified name for the class is org.apache.derby.iapi.sql.execute.ExecAggregator.

      Same problem exists in reference manual also.
      http://db.apache.org/derby/docs/dev/ref/rrefexcept71493.html

      1. DERBY-2676.patch
        0.7 kB
        Hiranya Jayathilaka

        Activity

        Hide
        Kathey Marsden added a comment -

        Abhilash, please unassign yourself from this issue if you are no longer working on it.

        Show
        Kathey Marsden added a comment - Abhilash, please unassign yourself from this issue if you are no longer working on it.
        Hide
        Hiranya Jayathilaka added a comment -

        This is a simple issue unfortunately without a patch. So here goes

        Show
        Hiranya Jayathilaka added a comment - This is a simple issue unfortunately without a patch. So here goes
        Hide
        Knut Anders Hatlen added a comment -

        Thanks for the patch!
        Committed revision 762122.

        I'm marking the issue as resolved even though the wrong class name is still used in the reference manual. I believe that generating a new list of error messages is one of the steps in the release process (http://wiki.apache.org/db-derby/DerbySnapshotOrRelease) so it will be done by someone else in a bulk operation later.

        Resetting assignee. Could one of the JIRA superusers add Hiranya to the derby-developers group so that the issue could be assigned to him?

        Show
        Knut Anders Hatlen added a comment - Thanks for the patch! Committed revision 762122. I'm marking the issue as resolved even though the wrong class name is still used in the reference manual. I believe that generating a new list of error messages is one of the steps in the release process ( http://wiki.apache.org/db-derby/DerbySnapshotOrRelease ) so it will be done by someone else in a bulk operation later. Resetting assignee. Could one of the JIRA superusers add Hiranya to the derby-developers group so that the issue could be assigned to him?
        Hide
        Kristian Waagan added a comment -

        Sure, I have added Hiranya to the derby-developers group. Welcome

        I also assigned the issue to him.

        Show
        Kristian Waagan added a comment - Sure, I have added Hiranya to the derby-developers group. Welcome I also assigned the issue to him.

          People

          • Assignee:
            Hiranya Jayathilaka
            Reporter:
            Tomohito Nakayama
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development