[jira] [Updated] (DERBY-5950) PlanExporter and SignatureChecker don't appear in the list of tools supported by derbyrun.

2016-01-29 Thread Yun Fang (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DERBY-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yun Fang updated DERBY-5950:

Attachment: run.java.diff
svn_status.txt
toolsmessages.properties.diff
toolsmessages_zh_CN.properties.diff

Here is the patchs for this bug and svn status info. The following tests is run:
1.
export LC_ALL=en_US.UTF-8
java -jar trunk/jars/sane/derbyrun.jar
2. 
java -jar trunk/jars/sane/derbyrun.jar PlanExporter
3. 
export LC_ALL=zh_CN.UTF-8
java -jar trunk/jars/sane/derbyrun.jar
4. 
java -jar trunk/jars/sane/derbyrun.jar PlanExporter

> PlanExporter and SignatureChecker don't appear in the list of tools supported 
> by derbyrun.
> --
>
> Key: DERBY-5950
> URL: https://issues.apache.org/jira/browse/DERBY-5950
> Project: Derby
>  Issue Type: Bug
>  Components: Tools
>Affects Versions: 10.10.1.1
>Reporter: Rick Hillegas
>Assignee: Yun Fang
>  Labels: derby_triage10_11
> Attachments: run.java.diff, svn_status.txt, 
> toolsmessages.properties.diff, toolsmessages_zh_CN.properties.diff
>
>
> The help message for derbyrun does not mention PlanExporter or 
> SignatureChecker. It should.
> java -jar trunk/jars/sane/derbyrun.jar
> Usage:
> java -jar derbyrun.jar ij [-p propertiesfile] [sql script]
> java -jar derbyrun.jar sysinfo [-cp ...] [-cp help] 
> java -jar derbyrun.jar dblook [args] (or no arguments for usage)
> java -jar derbyrun.jar server [args] (or no arguments for usage)
> Note that SignatureChecker can still be invoked via derbyrun. However, 
> PlanExporter can't:
> java -jar trunk/jars/sane/derbyrun.jar SignatureChecker
> Usage if running on J2SE:
>  
>   java org.apache.derby.tools.SignatureChecker  connectionUrlToDatabase
>  
> Usage if running on J2ME:
>  
>   java org.apache.derby.tools.SignatureChecker databaseName
> java -jar trunk/jars/sane/derbyrun.jar PlanExporter
> Usage:
> java -jar derbyrun.jar ij [-p propertiesfile] [sql script]
> java -jar derbyrun.jar sysinfo [-cp ...] [-cp help] 
> java -jar derbyrun.jar dblook [args] (or no arguments for usage)
> java -jar derbyrun.jar server [args] (or no arguments for usage)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: Derby-JaCoCo #211

2016-01-29 Thread Apache Jenkins Server 
See 

Changes:

[bpendleton] DERBY-5944: The hard-coded PlanExporter help message should be 
internationalized

This patch was contributed by  Yun Fang ( fangyuncn at gmail dot com  )

This change replaces the literal string text in PlanExporter.java with
references to Derby messages.

The change also contributes both the English message text and the corresponding
Chinese message text.

--
[...truncated 1645 lines...]
declare-autoloadable-driver:
[mkdir] Created dir: 


make-core-derbyjar-manifest:

make-locale-classpath-manifest:
  [jar] Building jar: 


derbytoolsjar:
 [echo] Beginning derbytools.jar insane build
 [echo]  creating tools.list 
 [echo]  creating new tools.properties file 

infowriter:
[propertyfile] Updating property file: 


meta-inf-common:
 [copy] Copying 2 files to 


make-locale-classpath-manifest:
  [jar] Building jar: 


derbynetjar:
 [echo] Beginning derbynet.jar insane build
 [echo]  creating net.list
 [java] SANITY >>> 
/org/apache/derby/impl/drda/NetworkServerControlImpl.class
 [java] SANITY >>> /org/apache/derby/impl/drda/AppRequester.class
 [java] SANITY >>> /org/apache/derby/impl/drda/DDMWriter.class
 [java] SANITY >>> /org/apache/derby/impl/drda/Utf8CcsidManager.class
 [java] SANITY >>> /org/apache/derby/impl/drda/DRDAProtocolException.class
 [java] SANITY >>> /org/apache/derby/impl/drda/EXTDTAInputStream.class
 [java] SANITY >>> /org/apache/derby/impl/drda/DRDAXAProtocol.class
 [java] SANITY >>> /org/apache/derby/impl/drda/DDMReader.class
 [java] SANITY >>> /org/apache/derby/impl/drda/DRDAConnThread.class
 [echo]  creating new net.properties file 

infowriter:
[propertyfile] Updating property file: 


meta-inf-common:
 [copy] Copying 2 files to 

  [jar] Building jar: 


derbyclientjar:
 [echo] Beginning derbyclient.jar insane build
 [copy] Copying 1 file to 


derbyclientjar.1.8:
 [java] SANITY >>> /org/apache/derby/shared/common/i18n/MessageUtil.class
 [java] SANITY >>> /org/apache/derby/client/am/LogWriter.class
 [java] SANITY >>> /org/apache/derby/client/am/BlobLocatorOutputStream.class
 [java] SANITY >>> /org/apache/derby/client/am/ClientConnection.class
 [java] SANITY >>> /org/apache/derby/client/am/ClobLocatorReader.class
 [java] SANITY >>> /org/apache/derby/client/net/NetConnection.class
 [java] SANITY >>> /org/apache/derby/client/net/NetAgent.class
 [java] SANITY >>> /org/apache/derby/client/am/ClientResultSet.class
 [java] SANITY >>> /org/apache/derby/client/am/BlobLocatorInputStream.class
 [java] SANITY >>> /org/apache/derby/client/net/NetCursor.class
 [java] SANITY >>> 
/org/apache/derby/client/am/StatementCacheInteractor.class
 [java] SANITY >>> /org/apache/derby/client/am/LogicalStatementEntity.class
 [java] SANITY >>> /org/apache/derby/client/am/stmtcache/StatementKey.class
 [java] SANITY >>> 
/org/apache/derby/client/am/stmtcache/JDBCStatementCache.class
 [java] SANITY >>> 
/org/apache/derby/client/am/stmtcache/JDBCStatementCache$BoundedLinkedHashMap.class
 [java] SANITY >>> /org/apache/derby/client/am/EncryptionManager.class
 [java] SANITY >>> /org/apache/derby/client/net/NetConnectionReply.class
 [java] SANITY >>> /org/apache/derby/client/net/Request.class
 [java] SANITY >>> /org/apache/derby/client/am/ClientStatement.class
 [java] SANITY >>> /org/apache/derby/iapi/services/info/JVMInfo.class
 [java] SANITY >>> 
/org/apache/derby/client/am/ClientPreparedStatement$PossibleTypes.class
 [java] SANITY >>> 
/org/apache/derby/client/am/CachingLogicalConnection.class
 [java] SANITY >>> /org/apache/derby/client/am/ClobLocatorInputStream.class
 [java] SANITY >>> /org/apache/derby/client/ClientXid.class
 [echo]  creating new dnc.properties file 

infowriter:
[propertyfile] Updating property file: 


meta-inf-common:
 [copy] Copying 2 files to

[jira] [Commented] (DERBY-6858) Apache Derby simple update statement performance becomes 1500% worse when adding one byte to a column

2016-01-29 Thread somebody (JIRA) 

[ 
https://issues.apache.org/jira/browse/DERBY-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124411#comment-15124411
 ] 

somebody commented on DERBY-6858:
-

Hi Bryan,

Did u have any luck fixing this issue?

> Apache Derby simple update statement performance becomes 1500% worse when 
> adding one byte to a column
> -
>
> Key: DERBY-6858
> URL: https://issues.apache.org/jira/browse/DERBY-6858
> Project: Derby
>  Issue Type: Bug
>Affects Versions: 10.11.1.1, 10.12.1.1
> Environment: windows 7 64 bit
>Reporter: somebody
>Priority: Blocker
> Attachments: repro.java, repro.java
>
>
> I have 2 tables as follows:
> ParentUpdate
> name varchar(255)
> value int not null
> primary key: name
> ChildUpdate
> parentName varchar(255)
> name varchar(255)
> value int
> data varchar(1000)
> primary key: name foreign key: parentName to ParentUpdate.name
> When I run the statement "update ChildUpdate set parentName = 'Parent 2' 
> where parentName = 'Parent 1'" with 2500 records in the ChildUpdate table and 
> 1 record in the ParentUpdate table with only a single byte difference in data 
> size in the ChildUpdate table, the performance decreases by 15 times.
> When the ChildUpdate data column has exactly 14 bytes of the same character 
> the runtime of the above query is about 500 milliseconds. When I add one more 
> byte to the data column of ChildUpdate the performance all of a sudden 
> becomes about 7500 milliseconds.
> If i then decrease the data size back to 14 from 15 it's fast again. When i 
> put it back to 15 it's slow again. This is reproducible every time.
> Can you please help me figure out how to get the same fast performance 
> without such seemingly random behaviour.
> The query plans are below for both cases.
> projection = true
> constructor time (milliseconds) = 0
> open time (milliseconds) = 0
> next time (milliseconds) = 16
> close time (milliseconds) = 16
> restriction time (milliseconds) = 0
> projection time (milliseconds) = 0
> optimizer estimated row count: 51.50
> optimizer estimated cost: 796.12
> Source result set:
> Table Scan ResultSet for CHILDUPDATE at read committed isolation 
> level using exclusive row locking chosen by the optimizer
> Number of opens = 1
> Rows seen = 2500
> Rows filtered = 0
> Fetch Size = 1
> constructor time (milliseconds) = 0
> open time (milliseconds) = 15
> next time (milliseconds) = 16
> close time (milliseconds) = 16
> next time in milliseconds/row = 0
> scan information:
> Bit set of columns fetched={0, 1}
> Number of columns fetched=2
> Number of pages visited=41
> Number of rows qualified=2500
> Number of rows visited=2500
> Scan type=heap
> start position:
> null
> stop position:
> null
> qualifiers:
> Column[0][0] Id: 0
> Operator: =
> Ordered nulls: false
> Unknown return value: false
> Negate comparison result: false
> optimizer estimated row count: 51.50
> optimizer estimated cost: 796.12
> total time: ~500 milliseconds
> and the slow version
>Statement Name: 
> null
> Statement Text: 
> update ChildUpdate set parentName = 'Parent 2' where parentName = 'Parent 
> 1'
> Parse Time: 0
> Bind Time: 0
> Optimize Time: 0
> Generate Time: 0
> Compile Time: 0
> Execute Time: -1453199485700
> Begin Compilation Timestamp : 2016-01-19 05:31:25.684
> End Compilation Timestamp : 2016-01-19 05:31:25.684
> Begin Execution Timestamp : 2016-01-19 05:31:25.7
> End Execution Timestamp : 2016-01-19 05:31:33.141
> Statement Execution Plan Text: 
> Update ResultSet using row locking:
> deferred: true
> Rows updated = 2500
> Indexes updated = 2
> Execute Time = -1453199485747
> Normalize ResultSet:
> Number of opens = 1
> Rows seen = 2500
> constructor time (milliseconds) = 0
> open time (milliseconds) = 0
> next time (milliseconds) = 47
> close time (milliseconds) = 0
> optimizer estimated row count: 51.50
> optimizer estimated cost: 810.94
> Source result set:
> Project-Restrict ResultSet (3):
> Number of opens = 1
> Rows seen = 2500
> Rows filtered = 0
> restriction = false
> projection = true
> constructor time

Jenkins build is back to normal : Derby-trunk #2430

2016-01-29 Thread Apache Jenkins Server 
See

[jira] [Commented] (DERBY-6857) Deprecate support for building Derby under JDKs 6 and 7

2016-01-29 Thread Rick Hillegas (JIRA) 

[ 
https://issues.apache.org/jira/browse/DERBY-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124745#comment-15124745
 ] 

Rick Hillegas commented on DERBY-6857:
--

Thanks for kicking the tires, Bryan. The full tests ran cleanly for me.

> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
>  Issue Type: Bug
>  Components: Build tools
>Affects Versions: 10.13.0.0
>Reporter: Rick Hillegas
> Attachments: ClassReferenceReader.java, Windows-sane-TypeId.class, 
> classReferenceComparison.txt, derby-6857-01-aa-remove6and7.diff, 
> derby-6857-02-aa-cleanupOldJdks.diff, derby-6857-03-aa-minimumVersion.diff, 
> derby-6857-04-aa-pruneConstantClasses.diff, jardriftcheck.diff, 
> mac-derby-jar-verbose.txt, mac-sane-TypeId.class, 
> windows-derby-jar-verbose.txt
>
>
> The community voted to stop supporting Java 6 and 7 as of release 10.13. See 
> the 2015-09-12 entry here: http://wiki.apache.org/db-derby/VoteResults. We no 
> longer need to support building Derby with those JDKs. This issue tracks 
> changes needed to remove that support and simplify the build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (DERBY-6857) Deprecate support for building Derby under JDKs 6 and 7

2016-01-29 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DERBY-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124747#comment-15124747
 ] 

ASF subversion and git services commented on DERBY-6857:


Commit 1727680 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1727680 ]

DERBY-6857: Make classlister prune the constants files from the rosters of jar 
file contents; commit derby-6857-04-aa-pruneConstantClasses.diff.

> Deprecate support for building Derby under JDKs 6 and 7
> ---
>
> Key: DERBY-6857
> URL: https://issues.apache.org/jira/browse/DERBY-6857
> Project: Derby
>  Issue Type: Bug
>  Components: Build tools
>Affects Versions: 10.13.0.0
>Reporter: Rick Hillegas
> Attachments: ClassReferenceReader.java, Windows-sane-TypeId.class, 
> classReferenceComparison.txt, derby-6857-01-aa-remove6and7.diff, 
> derby-6857-02-aa-cleanupOldJdks.diff, derby-6857-03-aa-minimumVersion.diff, 
> derby-6857-04-aa-pruneConstantClasses.diff, jardriftcheck.diff, 
> mac-derby-jar-verbose.txt, mac-sane-TypeId.class, 
> windows-derby-jar-verbose.txt
>
>
> The community voted to stop supporting Java 6 and 7 as of release 10.13. See 
> the 2015-09-12 entry here: http://wiki.apache.org/db-derby/VoteResults. We no 
> longer need to support building Derby with those JDKs. This issue tracks 
> changes needed to remove that support and simplify the build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)