db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1473) Add cut-off and truncation logic to streaming classes in the embedded driver
Date Thu, 10 Aug 2006 13:02:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1473?page=comments#action_12427201 ] 
            
Kristian Waagan commented on DERBY-1473:
----------------------------------------

Posting the results from my final derbyall runs for the patches 1a and 2a combined:
* Solaris 10 (x86)
  JDK 1.3 : 22 failures, 557 tests
  JDK 5.0 : 1 failure, 691 tests
                    upgradeTests/Upgrade_10_1_10_2.java
  JDK 6    : 2 failures, 734 tests
                   store/OnlineBackupTest1.java
                   upgradeTests/Upgrade_10_1_10_2.java
                     

* Linux (Gentoo 2.6.16, amd64)
   JDK 1.4  : 0 failures, 685 tests
   JDK 6     : 3 failures, 653 tests, derbynetmats skipped
                      derbynetclientmats/jdbcapi/XATest.java
                      lang/prediacatPushdown.sql
                      lang/wisconsin.java

I believe the upgradetest is failing because if my environment (not finding the jars).
The JDK1.3 errors are not due to my patch, but I will follow up on them.
predicatePushdown and wisconsin seem to choose different query plans.
Not sure about XATest, must look into the diff.

> Add cut-off and truncation logic to streaming classes in the embedded driver
> ----------------------------------------------------------------------------
>
>                 Key: DERBY-1473
>                 URL: http://issues.apache.org/jira/browse/DERBY-1473
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.2.0.0
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>             Fix For: 10.2.0.0
>
>         Attachments: derby-1473-1a-streaming.diff, derby-1473-1a-streaming.stat, derby-1473-2a-streamingtests.diff,
derby-1473-2a-streamingtests.stat
>
>
> When streaming data to Derby, the application stream will be wrapped in a Derby-specific
stream to convert the data to the correct representation. At a minimum, this consists of getting
the data to the on-disk format used by Derby.
> The wrapping stream can be extended to provide the following features at an earlier stage:
>  a) Data cut-off when the maximum allowed size is exceeded
>  b) Truncation of trailing blanks where allowed
> Both features can reduce the amount of data needed to be kept in memory on insertion.
> Implementing this will require additional column/data type information in the streaming
class(es). The implementation must be able to handle streams for which the length is specified
and also streams with unknown/unspecified length.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message