[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011827#comment-17011827 ] Richard N. Hillegas commented on DERBY-6809: I think that suggestions like that would need a lot of discussion by the broader community. I would recommend a separate email thread or JIRA for that discussion. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010671#comment-17010671 ] sagar commented on DERBY-6809: -- This should be possibly my last post here ... Just out of the blue a thought came to mind ... Derby has 3 modes of operation embedded, hybrid and networkserver. A question is why cant we operate Derby as a networkserver only ... and have a parameter in derby.properties files as mode ... SingleUser and MultiUser for Embedded and NetworkServer. When singleuser/embedded is chosen ... the NetworkServer will boot and run only on localhost:1527 and enable only one active connection at a time. Derby will ignore the host and port property in this case and also have a tight default java security policy in place and also run with a tight default securitymanager. For NetworkServer mode you can leave all the settings to the user. This way a lot of code specifically for Embeded mode and Hybrid mode can be left out and possibly NetworkServer and NetworkClientJDBCDriver can be more optimized and focussed upon. Just a wild thought. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009238#comment-17009238 ] Richard N. Hillegas commented on DERBY-6809: You can use whatever JDK you want to do your own development. I'm simply clarifying what JDK I use in order to build release distributions and to build/test contributions before I commit them. If someone posts a contribution which doesn't build or test cleanly against the committer's environment, then there will be a follow-on conversation. Realistically, I think that there is only a remote chance that the mismatch will be the result of using Amazon vs. OpenJDK. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008952#comment-17008952 ] sagar commented on DERBY-6809: -- Too much ambiguity in understanding of this oracle decision about jdk. I was under impression that even openjdk will be a forward only release that is new release every 6 months and no security updates or any LTS > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008947#comment-17008947 ] sagar commented on DERBY-6809: -- Openjdk is getting updates? I thought openjdk also will not have LTS and its updates for 3 years ... Thats prime reason i shifted to Amazon Corretto > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008849#comment-17008849 ] Richard N. Hillegas commented on DERBY-6809: I use the OpenJDK. Note that the JVM version used to build and run Derby is not the issue--provided that the license allows us to freely compile production code. The question for the community is the byte code level we generate. Cheers. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008816#comment-17008816 ] sagar commented on DERBY-6809: -- Great. Since Derby trunk compiles cleanly on Java 11 which I have checked and reported, think Java 11 could be considered especially now that Amazon Corretto is providing a patched well supported Java 11 LTS. Oracle LTS and licencing issues are all too confusing. One they say for non premium users LTS will not be patched. Yet they provide a download of JDK11.05 LTS on their website ... all too confusing. Amazon Coretto is a better option in my opinion. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008363#comment-17008363 ] Richard N. Hillegas commented on DERBY-6809: Thanks for volunteering to investigate these kinds of optimizations. It is likely that Derby performance would benefit from being run on more modern JVMs. Note that the current release policy is to compile Derby into Java 9 byte code. One practical consequence of this is that a submission can be committed only if it compiles cleanly on Java 9 and the tests pass on that JVM. We could, of course, hold a vote to move the byte code level forward to Java 11. That would make some sense since Java 11 is an LTS version and 9 isn't. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008237#comment-17008237 ] sagar commented on DERBY-6809: -- compiled successfully with min.version set to 11 since i am initially looking to pouch low hanging fruits do you think this could have some purely nano level benefits like compiler optimizations as java has progressed from 1.0 to 11.0 more elaborately would it produce a more efficient bytecode or more compiler options need to be programmed in? > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008179#comment-17008179 ] Richard N. Hillegas commented on DERBY-6809: The trunk is compiled into Java 9 byte code so that Derby will run on any module-aware JVM. The byte code level is set by the min.version variable in tools/ant/properties/defaultcompiler.properties. That variable, in turn, is picked up by the source and target attributes of all invocations in the build scripts. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008160#comment-17008160 ] sagar commented on DERBY-6809: -- Ok so one more good news from my side ... Text colorI decided to leave this IDE business aside and delete all previous checked out sources created projects and then I checked out the source code via command line ... latest trunk Installed ANT and built the derby jars using ant clobber ant buildsource ant buildjars all via command line. So that kind of gave me some high. No errors. JDK used was AMAZON CORRETTO openjdk version "11.0.5" 2019-10-15 LTS OpenJDK Runtime Environment *Corretto-11.0.5.10.1 (build 11.0.5+10-LTS)* OpenJDK 64-Bit Server VM *Corretto-11.0.5.10.1* (build 11.0.5+10-LTS, mixed mode) All I want to know is how to ensure that Binary format of class files is jdk11 or 11 ... where do you set it in ant build.xml > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008128#comment-17008128 ] sagar commented on DERBY-6809: -- Richard thanks for the heads up ... yes the project in the tools/ide directory is pretty old ... requires quite some work to make it work properly. Can try time permitting ... since I am so new to derby development (yes I know its been 2 yrs since I first made up my mind to contribute) I will need some time to understand and make changes to the existing nbproject folder. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008105#comment-17008105 ] sagar commented on DERBY-6809: -- Also are we producing the class files in java 1.4 format? Is there any setting inaven or ant for the same since when i opened the project in netbeans n also eclipse it showed target class file 1.4 > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008104#comment-17008104 ] sagar commented on DERBY-6809: -- Will check out though if i can be of any help to update project in that folder ... But will target Netbeans 11. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008103#comment-17008103 ] sagar commented on DERBY-6809: -- Can u recommend ide to use? But then when i checked out the 10.14 a year ago .. i just opened using netbeans and it opened With these new sources ... I open the maven2 project n it has a issues mentioned above. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008092#comment-17008092 ] Richard N. Hillegas commented on DERBY-6809: The netbeans project under trunk/tools/ide/netbeans has not been updated since 2016. I would not expect it to work with the current state of the trunk after the modularization work done for Derby 10.15. The netbeans project needs to be updated by someone who knows how to configure that ide--I don't use it myself. If no-one volunteers for that task, then maybe we should remove it so that it doesn't cause confusion. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007981#comment-17007981 ] sagar commented on DERBY-6809: -- When I checked out 10.14 long time back and opened the project using Netbeans 8.2 ... bingo it opened very well with all sources listed ... Check attached screenshot nb8.png But now when I checked out latest trunk and opened the project using Netbeans no sign of sources in the Projects or the Files tab tree. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, latest.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007808#comment-17007808 ] Davide Grandi commented on DERBY-6809: -- I started with Ant, followed the instructions in [http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co] (the same in trunk's root), got a successfully build (buildsource and buildjars) and then tweaked some external Eclipse projects to familiarize with sources. Being Netbeans more Ant-oriented you'll should find your path with more easyness. Bye, Davide. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, latest.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007713#comment-17007713 ] sagar commented on DERBY-6809: -- Happy New Year to you too and the Team Derby. Yes steep learning curve awaits for achieving LOW HANGING FRUIT which started this all. Have checked out the sources and opened the maven2 project in Netbeans and on clicking Build I get the following error ... No idea why derbyshared.jar is required ??? Isnt it supposed to be built via these sources itself. Secondly no idea why the sources are not listed in Netbeans ... Havent used Maven in Netbeans ... I see no sources in Netbeans and DItto in Eclipse. cd /home/sagars/NetBeansProjects/derby/derby/maven2/commons; JAVA_HOME=/home/sagars/amazon-corretto-11.0.5.10.1-linux-x64 /home/sagars/netbeans/java/maven/bin/mvn --errors -e install Error stacktraces are turned on. Scanning for projects... Building Apache Derby Shared Code ALPHA_VERSION --- maven-remote-resources-plugin:1.2.1:process (default) @ derbyshared --- --- maven-resources-plugin:2.5:resources (default-resources) @ derbyshared --- [debug] execute contextualize Using 'UTF-8' encoding to copy filtered resources. skip non existing resourceDirectory /home/sagars/NetBeansProjects/derby/derby/maven2/commons/src/main/resources Copying 3 resources --- maven-compiler-plugin:2.3.2:compile (default-compile) @ derbyshared --- No sources to compile --- maven-resources-plugin:2.5:testResources (default-testResources) @ derbyshared --- [debug] execute contextualize Using 'UTF-8' encoding to copy filtered resources. skip non existing resourceDirectory /home/sagars/NetBeansProjects/derby/derby/maven2/commons/src/test/resources Copying 3 resources --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ derbyshared --- No sources to compile --- maven-surefire-plugin:2.9:test (default-test) @ derbyshared --- Surefire report directory: /home/sagars/NetBeansProjects/derby/derby/maven2/commons/target/surefire-reports --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 --- maven-jar-plugin:2.3.1:jar (default-jar) @ derbyshared --- Building jar: /home/sagars/NetBeansProjects/derby/derby/maven2/commons/target/derbyshared-ALPHA_VERSION.jar --- maven-site-plugin:3.0:attach-descriptor (attach-descriptor) @ derbyshared --- --- maven-antrun-plugin:1.6:run (default) @ derbyshared --- Parameter tasks is deprecated, use target instead Executing tasks main: BUILD FAILURE Total time: 6.139 s Finished at: 2020-01-04T01:05:46+05:30 Final Memory: 16M/57M Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.6:run (default) on project derbyshared: An Ant BuildException has occured: Warning: Could not find file /home/sagars/NetBeansProjects/derby/derby/jars/insane/derbyshared.jar to copy. -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.6:run (default) on project derbyshared: An Ant BuildException has occured: Warning: Could not find file /home/sagars/NetBeansProjects/derby/derby/jars/insane/derbyshared.jar to copy. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jd
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007710#comment-17007710 ] Bryan Pendleton commented on DERBY-6809: Glad to see you back, happy new year! Yes, the trunk branch is the correct one to use for developing new features > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, latest.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007628#comment-17007628 ] sagar commented on DERBY-6809: -- Sorry once again I am posting this ... this year may find time to take this forward ... Kingly confirm if I have checked out the correct code for the work. The screenshot name is latest.png > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282756#comment-16282756 ] Rick Hillegas commented on DERBY-6809: -- Q> And a final thought ... Any work on derby MVCC going on? A> The discussion is usually very short. MVCC would be an entirely new storage engine. No-one has volunteered for that big project. Q> And also a pluggable NOSQL or added NOSQL? A> NOSQL covers a lot of functionality. It's hard to know what people mean by the term. a) Sometimes it's just the ability to import data from a schema-free format like JSON. There is an optional tool for importing simple JSON objects and for flattening them into rows, and also for exporting query results in JSON format. See http://db.apache.org/derby/docs/10.14/tools/rtoolsoptsimplejson.html This support could definitely be built out. Similar optional tools could also be written for other popular hierarchical and non-tabular formats like AVRO and PROTOBUF. Writing optional tools like that would be an area in which newcomers could contribute quickly because they wouldn't have to learn the intricate details of Derby's internals. b) Sometimes people mean the ability to store hierarchical formats in a way which Derby's SQL engine could query efficiently. These are big projects for which no-one has volunteered. c) Sometimes people mean an efficient federated query engine which could marry data from relational and non-relational sources. Again, that's a big project without any volunteers. And you may means something else by the term NOSQL. Q> And that famously asked for demanded one Optimistic Locking? A> No-one has volunteered for this one either. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281584#comment-16281584 ] sagar commented on DERBY-6809: -- Yes. Now it me and my interia. I dont know how significantly I will be able to contribute but will get over the Inertia and make a start. DERBY because I have used it. And I liked what I used. And I believe it can be further of use to many who still dont use it or are not even aware of its existence as a DB which is a perfect replacement for MS ACCESS and likes but much stable powerful and reliable with ACID at least. And a final thought ... Any work on derby MVCC going on? And also a pluggable NOSQL or added NOSQL? > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281216#comment-16281216 ] Rick Hillegas commented on DERBY-6809: -- Looks like Knut and Bryan have answered your questions. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280269#comment-16280269 ] Bryan Pendleton commented on DERBY-6809: Changes to the code, unless they are emergency bug fixes, should be introduced on the trunk, so you should definitely be working on the trunk. You should have a look at: # http://db.apache.org/derby/derby_comm.html#Contribute+Code+or+Documentation # https://wiki.apache.org/db-derby/ForNewDevelopers # https://wiki.apache.org/db-derby/DerbyContributorChecklist # https://wiki.apache.org/db-derby/DerbyDev As you assemble concrete proposals for specific changes, may I suggest the following? # For each such proposal, open a new JIRA "sub-task" of this JIRA issue. # Describe the specific change that you recommend for Derby, and any needed background to it # Attach the proposed changes to that sub-task, using the tools and formats and processes recommended in the above links That process helps the community incorporate your improvements in as straightforward and rapid a manner as possible. Thanks! > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279703#comment-16279703 ] sagar commented on DERBY-6809: -- Rick, what do you suggest. Do I work off the current devel trunk or on the branch I checked out. Java 9 with Netbeans 9 is still a WIP. Usable though. Also, would like to know, if I make if and where do I commit for a review? Though most initial would be only supportive ones like @Override annotations some @param tags in docs AIC to Lambdas etc. Real heads up would take time since study would be required on the Architecture and coding. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278419#comment-16278419 ] Knut Anders Hatlen commented on DERBY-6809: --- Some examples: DERBY-2150 Reduce use of synchronized collections in GenericLanguageConnectionContext DERBY-2493 Use unsynchronized collections in BackingStoreHashtable DERBY-2911 Implement a buffer manager using java.util.concurrent classes DERBY-3092 Use java.util.concurrent in TransactionTable to improve scalability DERBY-6075 Use modern collections in impl/sql/compile > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278391#comment-16278391 ] sagar commented on DERBY-6809: -- Ok. So a safe place to start. The sort package has ample use of Vectors. Knut, any example where exactly the replacement was made just as a reference. True, there could not be a major measurable improvement by replacing the Vector in a mergesort but as you said, I still am unable to read the mind of the original programmer of this code as to why a Vector (synchronized datatype) was used in the first place. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278298#comment-16278298 ] Knut Anders Hatlen commented on DERBY-6809: --- I haven't studied all the details of MergeInserter, but it looks like an ArrayList might be safe to use there. This code probably predates the introduction of ArrayList in Java, so Vector was the only alternative at the time. We replaced some Vectors with more modern collections a while ago, but that work focused on the synchronized collections that were performance bottlenecks. I doubt that it will be possible to measure any performance impact of a couple of synchronized operations per temporary file in a merge sort, but it still might be good to change it. If nothing else, readers of the code won't need to spend time figuring out why a synchronized collection is used. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278051#comment-16278051 ] sagar commented on DERBY-6809: -- Hi Rick Two questions. I checked out 10.14 as its on Java 1.8 which I have right now. Dunno if and when I would want to be a committer. Still early days. I could make few changes to small part and then commit in the branch possibly which someone could have a look at and then pull it up to the main TRUNK. Any other direction suggestion for me would be welcome. Better have someone throw light than Exception. Secondly as you can see, I have got started somewhere. So, if Vectors were replaced then they either missed out a few or the commit wasnt merged. But my question was specifically to the org.apache.derby.impl.store.access.sort.MergeInserter class and if it was safe to replace Vectors with unsynchronized Collections. The reason for the question is that since Vectors were used it means the Author wanted synchronized gurantee. And if thats the case then we can use modern optimized Concurrency enabled Collections. Also, I will evaluate each and every change as small as this (using a different type) for performance scalability balance and then make decisions, is what I have thought. I also understand that just because there is C programming language, I shouldnt go about replacing Assembly Code blindly. Thats the base direction I have kept for myself. But also, I have assumed that the JAVA COMPILER and JVM will get smarter and optimized in the future and hence something of an overhead today will get auto optimized by the future compiler. for eg. LAMBDAS vs AIC ... Depends on scenarios but the hope of future enhancements in LAMBDAS makes me replace AIC with LAMBDAS. Also, since derby is a server or a long running process, I feel that out of the box LAMBDAS will make DERBY faster than AIC, as with frequent calls LAMBDAS will perform better for a long running process. Currently, my approach is purely horizontal to check if there can be an easy low hanging fruit to be consumed without too much effort but by making a full pass to each and every file. So awaiting direction on which codebase to start on. Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277907#comment-16277907 ] Rick Hillegas commented on DERBY-6809: -- Your screenshot indicates that you have checked out the 10.14 branch. At this point, that is a bugfix branch. Development is going on in the trunk at https://svn.apache.org/repos/asf/db/derby/code/trunk/ I don't see why more modern list structures couldn't be used. I recall that Knut Anders Hatlen and others made a pass through the codeline many years ago, replacing Vectors with unsynchronized structures. Maybe Knut has other insights. Thanks, -Rick > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276594#comment-16276594 ] sagar commented on DERBY-6809: -- org.apache.derby.impl.store.access.sort.MergeInserter Vector has been used. Is it really needed? Does it need the thread safety? Can it be replaced by ArrayList? If thread safety is required then can we use Collections.synchronizedList or CopyOnWriteArrayList? > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > Attachments: 2017-12-04-143613_1366x768_scrot.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276484#comment-16276484 ] sagar commented on DERBY-6809: -- Am attaching a screenshot of checkout. Kindly guide if correct. sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275430#comment-16275430 ] sagar commented on DERBY-6809: -- And yes, I dont know why DERBY is a legacy product. Very stable. Mature indeed. And trustworthy. Kudos to all the efforts to keep it going and not moving away from CORE STRENGTHS ... SIMPLE, ACID and STABLE. In fact I see it being used as CLOUD based DB, MS ACCESS replacement with more features, ORACLE EXPRESS EDITION replacement, and hope someone writes an APEX like WYSIWYG DECLARATIVE tool for DERBY. If I can even get started in my lifetime on any of the above, I would be at peace with myself sitting in the CLOUDS ABOVE. Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275429#comment-16275429 ] sagar commented on DERBY-6809: -- Almost clear. Except for if and where there are any architecture documents. Agree RISK is not something on priority right now. I would go with existing base and moving towards more DB features, bug fixes and enhancements. But just just thinking if a branch in GIT could exist for this RISK but not pulled in into main. Those who want to PUSH, will keep pushing in this branch. How about in the 10.15. Although I am myself not very sure when I will be ready to do a PUSH there in the RISK branch. Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275359#comment-16275359 ] Bryan Pendleton commented on DERBY-6809: Oh, I think we could make a stronger statement than that? Surely, rewriting the 20-year-old Derby code base to take advantage of the latest features of the Java language has *TREMENDOUS* potential. The code could be smaller, faster, clearer, and more reliable. It could be much easier to add new features. It could allow us to use auxiliary development tools which are oriented around the latest Java features. However, rewriting code is (a) tedious, and, much more importantly, (b) risky. We have a low appetite for risk, right now. We are blessed in that we have a rich and varied test bed, with 20 years of accumulated test suites, which can support us as we refactor and improve the code. We are, however, also impoverished in that, being largely a mature and "legacy" product, we have a small active developer base, particularly relative to the size and complexity of the code base. To seriously consider rewriting large parts of the Derby engine, we'd need to have 10-20 committed, active developers, such as was the case when several large corporations were actively supporting this project. Anyway, I have no idea where I'm going with this, just wanted to share my perspective. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275164#comment-16275164 ] Rick Hillegas commented on DERBY-6809: -- Q> Do you think that rewriting code with new enhancements in JAVA Language will be beneficial to DERBY from any point of view. A> Derby could take advantage of Java's support for parallel operators. Q> Also, is there a SPECIFIC ARCHITECTURE DOCUMENT of Derby somewhere which will depict ARCHITECTURE and source code organization. A> Take a look at the architecture documents at http://db.apache.org/derby/blogs/index.html. Click on "Papers and Presentations" in the left sidebar and then click on "Derby Engine" Hope this helps, -Rick > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274124#comment-16274124 ] sagar commented on DERBY-6809: -- Hi Rick, Thanks for the detailed reply. Couple of more questions. Do you think that rewriting code with new enhancements in JAVA Language will be beneficial to DERBY from any point of view. Theoretically, without having had a detailed look at the architecture and code, I feel there may be chances of improvement. Dunno if practically that effort would yield noticeable improvements. Experienced developers in DERBY should be able to throw some light on this. I am referring to performance improvements in newer JAVA versions if they can be incorporated. Language improvements and new Features, would not always be performance related. Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273660#comment-16273660 ] Rick Hillegas commented on DERBY-6809: -- Q> Also, does derby still compile to Java 6 bytecode or now say 10.15 will always compile to Java 9 bytecode? I assume the later. A> 10.15 compiles into Java 9 bytecode. Q> Another suggestion, can 10.15 be a long term supported release. As in, future bug fixes and features will be available for this release too. Backported if you can say so. A> For the past several years, Derby has produced a new release family (10.12, 10.13, 10.14) once a year, often with a maintenance release roughly half way inbetween. Once we move onto the next release family, there is little motivation to produce an official maintenance release on any earlier family. However, bug fixes can be (and often are) ported to older release families. Anyone can build a distribution from one of these patched families. If you are concerned about a particular bug fix, please let the committers know so that they can backport the fix to the target you need. Q> I assume that we are dropping support for older JAVA versions but not necessarily rewriting the code to support and take advantages of new features in JAVA latest versions. A> I'm not aware that anyone is working on a large-scale re-write of the existing code base in order to take advantage of new Java features. However, the code was rototilled significantly so that it compiles cleanly, without warnings, under Java 9. Contributors do take advantage of new language features when writing new code, of course. Q> Essentially this will help interested developers do try and rewrite DERBY code to take advantage of newer features. A> Derby is already divided fairly cleanly into independent components. Hopefully, that component architecture will become clearer and cleaner as we proceed with our effort to divide 10.15 into Jigsaw-ready modules. If you are planning to re-write the Derby code, I highly recommend that you design your changes so that your new code will appear as a new implementation of an existing component. That will make it easier to evaluate and package your changes as the community accepts them. Thanks, -Rick > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272168#comment-16272168 ] sagar commented on DERBY-6809: -- Read it already. So, another suggestion, can 10.15 be a long term supported release. As in, future bug fixes and features will be available for this release too. Backported if you can say so. I assume that we are dropping support for older JAVA versions but not necessarily rewriting the code to support and take advantages of new features in JAVA latest versions. Essentially this will help interested developers do try and rewrite DERBY code to take advantage of newer features. There could then be two branches of DEVELOPERS for DERBY ... one that will look into JAVA implementation and one that will look into the database part SQL compliances and features additions. Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271745#comment-16271745 ] Rick Hillegas commented on DERBY-6809: -- Note that the next feature release (10.15) will be targetted at Java 9. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270592#comment-16270592 ] sagar commented on DERBY-6809: -- Hello Rick, Though I have not been able to find time to get going on this issue, I am very happy to see this http://db.apache.org/derby/derby_downloads.html which now lists DERBY RELEASES for specific JDK versions. Great that the first move has been made. Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577782#comment-14577782 ] Rick Hillegas commented on DERBY-6809: -- Hi Sagar, Suppose that you use subversion to check out the 10.11 branch and then build that code by following the instructions here: http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co. In that case, you will get a debug build which is appropriate for development. The release id of your jar files will be the release id of the head of the 10.11 branch (10.11.1.3). Production distributions (the lib and bin distributions of a Derby release) are built without that debug machinery. To get a production distribution, you can set "sane=false" in your ant.properties file. I think that you want to start out with the default, debug build which is appropriate for Derby developers. Hope that we aren't talking past one another. -Rick > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576629#comment-14576629 ] sagar commented on DERBY-6809: -- Hi Mike java/engine/org/apache/derby/impl/store/access/sort I think almost all Files in this package need to be rewritten to take fukll advantage of the java8 collections api. Comment. Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576603#comment-14576603 ] sagar commented on DERBY-6809: -- Hi Rick Thanks. That was understood ... my question was regarding the settings need to be done described in BUILDING DERBY ... All I wanted to know if once I download the source code lets say the production 10.11.1.1 ... Will all the buid configs have the same settings as the production build 10.11.1.1 jar files ... Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576307#comment-14576307 ] Rick Hillegas commented on DERBY-6809: -- Hi Sagar, Note that you cannot build a production release from the development trunk in its current state. A release built from the trunk right now will be an alpha release, that is, one which you can't upgrade from. However, we will be cutting a 10.12 release branch later this year. You will be able to build a production release from that branch. If you need a production release now, I recommend that you port your work to the 10.11 branch. Hope this helps, -Rick > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566531#comment-14566531 ] sagar commented on DERBY-6809: -- Ok, started some preliminary work ... this is going to take time ... Firstly, I do understand that PARALLELISM for each and everything will end up doing more harm than good ... I am on this, first in theory ... 1. Can there be something as intelligent PARALLELISM? 2. Newer facilities in JAVA8, is it only to make code readable? Fewer lines of code? 3. Is the PARALLELISM real in STREAMS and LAMDAS or is it pseudo pr as mentioned here http://coopsoft.com/ar/Calamity2Article.html#para is it PARAQUENTIAL? 4. In a multithreaded environment such as J2EE Servlet Container, a Connection pool and then DERBY as a network server ... will PARALLELISM within the DERBY CODE ITSELF be blocking affect performance or will it benefit? Can there be newer techniques which can be thought of which will remove the perceived demonstrated and theoretical drawbacks? Will work on the above first ... seek answers of my own ... and wait for a lot of inputs and words of wisdom too ... Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566097#comment-14566097 ] sagar commented on DERBY-6809: -- And finally though derby is popular mostly as an embedded database or an in memory database most of my thinking is oriented toward derby as a network client server traditional database. Dunno if thats right And hence the thought of using the multicore improvements and full support in the new Java8 so that better performance is achieved when there are 100s or even thousands of concurrent users via a webapp using a connection pool ... > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566092#comment-14566092 ] sagar commented on DERBY-6809: -- Hello All Though this is not the right place to ask, before I checkout trunk, does it have all the settings for the build which produce a release? That is if I check out the trunk, will all the build configs and parameters and knobs and properties be same as they are on the recent stable build binary available on derby site or I have to manually configure all the properties and settings before I click build? Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566080#comment-14566080 ] sagar commented on DERBY-6809: -- Hi Mike just went through all the *.java in java/engine/org/apache/derby/impl/store/access/sort Wow ... so easy and trivial ... no wonder its left to the new developers rather than the senior pros ... Freshers have to be content with doing trivial stuff isnt't it? :) :) :) Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566052#comment-14566052 ] Mike Matrigali commented on DERBY-6809: --- See derby.storage.sortBufferMax property use in derby tests and the sort code for a tuning knob that is useful for writing developer tests to control in memory vs external sort. This knob is not meant for public use as it is hard to document in terms an application would prefer. It controls number of sort items rather than amount of memory.Not sure if java still gives app code a good way to know how much memory is being used for N rows containing user data of varying types and lengths. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566050#comment-14566050 ] Mike Matrigali commented on DERBY-6809: --- Some generic comments on possible improvements in the sorted not specific to java 1.8 feature use. The sorter is an area of the system that should be easy for a new derby developer to contribute to. The current base implementation has changed very little than what was put together for the initial release of the closed source Cloudscape system. All the code is localized in java/engine/org/apache/derby/impl/store/access/sort. Sort is used mainly for 2 things in derby: index creation and SQL order by. Hardly any work has been done on improving index creation performance, not many requests. Some number of apps create indexes when table is empty so sort not an issue. Other percentage of derby use has relatively small tables so again not an issue. For order by performance most problem queries are better served by sort avoidance (by having the right indexes) rather than improved order by. Even though not a lot of work has been done, I do believe there is room for improvement. Probably easiest would be to get community to agree to update the default sort size, and probably at same time provide a documented knob so that if that broke old applications one could dial it back. Current code attempts to keep memory usage around 1 meg per sort. An interesting first step might be to just provide an implementation of sort that uses modern jvm collections (which did not exist when code was first implemented) and compare to the hand coded sort implementation. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566034#comment-14566034 ] Mike Matrigali commented on DERBY-6809: --- I see no reason to work off any version before 10.11. I always work off whatever version is the top of trunk, which would be some version of 10.12 I believe for now. It seems like the work you are doing is new feature rather than bug fixing so when it is ready for commit the only appropriate place would be trunk. If you want to compare just your changes to what you are seeing in 10.11 than you can choose to work off of 10.11. I would recommend working off the top of the 10.11 branch, which likely is very close to what you are running but will include whatever bug fixes have been backported since the 10.11. Committers will still prefer to see patches based off of trunk. Svn can be used to apply patches off one version to another. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564716#comment-14564716 ] sagar commented on DERBY-6809: -- Hi Mike, Will get started soon as have todo this in really free time I get ... Secondly with regards to the sorter, the threshhold you are talking that can be bumped up ... is it a derby.xx.xx kind of a setting in derby,properties or it something in the code (like hardcoded) .. Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552425#comment-14552425 ] Mike Matrigali commented on DERBY-6809: --- i would add that you should make sure to not order by any key/key set that already has an index as Derby will try it's best to eliminate sorts by using the index. For a test case easily done just by not having any indexes. The sample size seems small to me but depends on data length. I would suggest designing your test case to be able to generate N rows of data and then pick whatever order of magnitude number of rows takes seconds to run. I find that amount of work significant enough to usually give good results, but not too long so that you can do iterative debugging easily. Later longer runs may be interesting. There are 2 paths through the sorter. One tries to do everything in memory, the other splits the problem up into groups and writes/reads merge runs from/to disk. The threshold is based on optimizer estimate of amount of data. Off hand I do not remember the default and there is some knob that can be used to bump it up. The default is likely too small for most applications that have huge amounts of memory. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551765#comment-14551765 ] sagar commented on DERBY-6809: -- Hi Rick, Thanks. OMG the pressure n onus on me now ... things easier said than done ... :) :) At a very very high level, I assume that Order By sql clause will map to the SortFactory which will sort the results ... Is this so? And to check any benefits, I need to have at least 10 rows of assorted random text data and numeric data and check the metrics if there is any benefit ... is this sample ok? Regards, Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551211#comment-14551211 ] Rick Hillegas commented on DERBY-6809: -- Hi Sagar, Derby's modules are classes which implement the org.apache.derby.iapi.services.monitor.ModuleControl interface. These modules are listed in java/engine/org/apache/derby/modules.properties. Some of these modules are platform-specific. The header comment in that file is a little stale and a little cryptic, but it explains the mechanism by which Derby decides which version of a module to load. I recommend following the pattern used by the 2 implementations of the JDBC driver module (InternalDriver and Driver42). If you are interested in sorting, then I recommend that you start out trying to implement a Java 8 version of the SortFactory module. Right now there is only one, platform-agnostic version of that module. It is described in modules.properties by these lines: derby.module.access.sort=org.apache.derby.impl.store.access.sort.ExternalSortFactory cloudscape.config.access.sort=all I'm a little rusty here, but I think that what you need to do is change those lines to the following in order to say that ExternalSortFactory is used for Java 6 and 7... derby.module.access.sort6=org.apache.derby.impl.store.access.sort.ExternalSortFactory derby.env.jdk.access.sort6=7 cloudscape.config.access.sort6=derby ...and then add another block of directives to describe the Java 8 sort factory which you are going to write... derby.module.access.sort8=org.apache.derby.impl.store.access.sort.MyJava8SortFactory derby.env.jdk.access.sort8=9 cloudscape.config.access.sort8=derby You may have to play around with this. It's a little tricky. Hope this helps, -Rick > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549981#comment-14549981 ] sagar commented on DERBY-6809: -- And of course I am using DERBY 10.11.1.1 in production on 64bit JAVA8 JVM ... On a IBM X3300 M4 Server 32GB ECC RAM Hardware RAID 10 on 500GB SAS INTEL XEON QUAD CORE PROCESSOR === But for performance optimization, especially the queries, the server in development is a simple machine with following specs AMD ATHLON 5150 Quad Core 8GB RAM 500GB HDD > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549812#comment-14549812 ] sagar commented on DERBY-6809: -- Hi Rick, Thanks. >From your reply,Dunno how a particular code executes only if a platform is >available (implementation)... any links to src file of the same in derby >codebase ... should get me started ... Though again java8 src is blackbox to me ... obviously its not possible that java8 provides increased parallelism to the java6 codebase transparently ... unless they have some artificial intelligence in the JIT and Runtime which detects such candidate bytecode and does it on the fly ... AFAIAC ... thats not what it is ... Yes am interested in performing some experiments very much but need someone (help) to point me to a particular piece of code or two or 3 source files ... yes low hanging fruit discovery will get the Java8 and future track started ... since its a huge huge task to convert the code manually to java8 So looking for some one to point to an implementation in src somewhere that uses collections sorting loop etc. which then can be converted and then tested against a query on both the default derby and the derby8 on jvm8. I still feel that even a 1% chance of 5% improvement in performance is worth taking since now the software (JVM) supports the hardware commonly available ... Thanks, Sagar > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549157#comment-14549157 ] Rick Hillegas commented on DERBY-6809: -- Most Derby code is compiled into Java 6 byte code. A small amount of code (chiefly in the implementation of the JDBC 4.1 and 4.2 drivers) is compiled into Java 7/8 byte code and only executes if you are running on those more capable platforms. I don't know whether the Java 8 libraries were implemented in such a way that they still provide increased parallelism to programs which were compiled into Java 6 byte code. That is, I don't know whether Derby's throughput increases if you simply run it on Java 8. But there is certainly nothing which prevents you from exploiting Java 8's increased parallelism in your user-written plugins (types, aggregates, functions, procedures). It sounds like you are interested in performing some experiments which might discover some low-hanging fruit. Thanks, -Rick > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547589#comment-14547589 ] sagar commented on DERBY-6809: -- And yes, conscious manual transition of source code to java8 is a big task ... hence the suggestion towards a testing parrallel build of derby8.jar wherein changes autosuggested by tools can be first incorporated ... Specifically related to IO, Concurrency, and Parallelism. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547584#comment-14547584 ] sagar commented on DERBY-6809: -- Hello Rick, Ok ... right and point taken on proceedures and functions ... but will a Java8 specific package of proceedures and functions run on the normal derby build if its running on jvm8? Thats point one ... Secondly, yes there is significant amount of work on manually changing the code to take advantage of Java8 features ... but proposal taking this into account, now more specifically is ... if we use some a tool like Netbeans which automatically suggests for eg. Convert to Lambda, etc ... can this be done to just put things moving on the Java8 parallelism track? Yes that means 2 builds a derby8 build targetting jvm8 only and the normal derby. Since the DERBY source code as of now is a black box to me ... I can only speculate that even a simple query like SELECT * FROM emp WHERE empname LIKE 'sa%' ORDER BY empage; could be benefited by the parallelism features assuming collections etc. are being used internally to sort filter order the final resultset ... benefits may not really be in terms of time (speed) always ... but taking advantage of hardware available certainly has benefits ... since now with JAVA8 you can truely take advantage of So in theory or principle if some expert confirms this, then probably I can find some time to modify some of the source code (auto hinted by Netbeans8) for a particular specific THING ... create a build and test it if there is a benefit using the default derby.jar and using the derby8.jar both running on a java8 jvm for that specific THING ... Guide and comment. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547400#comment-14547400 ] Rick Hillegas commented on DERBY-6809: -- I also am unclear on what is being proposed. There may be some low-hanging fruit, but I suspect that some significant development effort would be required to make the Derby engine take advantage of the Java 8 library support for parallelism. However, I don't see anything which stops users from writing procedures and functions which take advantage of the Java 8 libraries. Some work will be required to deprecate support for Java 6, but it should be minor compared to the work we had to do when we deprecated support for Java 1.4. I don't think there is anything other than tradition which prevents us from deprecating support for Java 6 and Java 7 in 10.12. We would want to vote on this, of course. But our attachment to old versions of Java may be weaker today than it was a year ago. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547390#comment-14547390 ] Rick Hillegas commented on DERBY-6809: -- Mike wondered whether there was an official place to record vote results. When I asked that question 10 years ago, I was told that the official record is the mail archive. Unofficially, we try to record vote results on the wiki: http://wiki.apache.org/db-derby/VoteResults But we don't record votes on release candidates on that wiki page. I don't know whether that page is missing other, important votes. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547198#comment-14547198 ] sagar commented on DERBY-6809: -- Thanks Mike ... Thing is not just java 7,8,9 support per se but specifically if code can be auto modified usig tools to take advantage of new language features specifically the lambdas n streams n collections n concurrency changes along with the new io enhancements and stronger encryptions in java8 ... then we can see performance benefits as well as security improvements ... software always played catch up to hardware advancements and now java 8 presents an opportunity to truely leverage the multicore processors so that even on a simple dualcore netbook the advantages can be seen which alloys software developers using derby in their products apps etc. to ve more flexible and have some more horizontal growth on their products ... so my point is not just be able to compile and run on newer java but take advantage of the neweer features in java new versions > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546998#comment-14546998 ] Mike Matrigali commented on DERBY-6809: --- There was a VOTE on sunsetting jdk6 support that passed: http://apache-database.10148.n7.nabble.com/RESULT-VOTE-Sunsetting-support-for-Java-6-td142158.html Is there an official place to find derby VOTE results? Here is what was decided: http://apache-database.10148.n7.nabble.com/VOTE-Sunsetting-support-for-Java-6-td141816.html#a142056 Please vote on the following proposed policy for supported platforms. The polls close at 5:00 pm San Francisco time on Monday September 15. A) The 10.12 release notes will tell users that 10.12 is the last release which supports Java 6. B) The 10.13 release will support Java 9, 8, and 7 as well as Java 8 compact profile 2. After releasing 10.12, the development trunk will no longer support Java 6. C) We expect that maintenance releases on a branch will continue to support the same Java versions as the initial feature release cut from that branch. We will document this on the wiki. D) Developers will need to keep in mind the porting implications of using modern JVM features in code which may need to be reworked to run on older JVMs. Some explanation will be helpful when exploiting a modern language feature for the first time. Adopting this policy would result in the following changes to the 10.13 trunk: I) Removing build support for Java 6. II) Purging user doc references to Java 6. We do not anticipate that this policy will require any changes to user code. Further discussion of this proposal can be found on the following email thread: http://apache-database.10148.n7.nabble.com/Java-6-vs-7-td141757.html > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546997#comment-14546997 ] Mike Matrigali commented on DERBY-6809: --- Not sure what exactly is being proposed. At one point in the past derby supported jdk14, but had jdk15 features that were enabled if you were running against a jdk15 jvm. If the file needed to be compiled with jdk15 compiler there was a mechanism in the build files to let the system know that. It is up to the developer of the code to make sure system still runs with existing capability if running on jdk14. There are mechanisms supported by the derby class loader to allow system to determine jvm level and then to load either a jdk14 or jdk15 version of the code that would implement the same interfaces. If what is being proposed is to desupport running with jdk17 and earlier versions of the jvm, in the past derby has given users at least a one release warning. The types of thing being proposed sound like features to me so should only be added to a future major release, not to the existing 10.11 release. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546914#comment-14546914 ] sagar commented on DERBY-6809: -- and if it can be done in 11 ... why not start with 10.11 series itself and release a java8 compiled derby with java8 functionality in a few derby areas ... especially query processing and results > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546908#comment-14546908 ] sagar commented on DERBY-6809: -- Java 8 parallel array operations to sort filter etc. ... using inbuilt mechanism provided by java8 api or lambdas and streams ... with the derby source code still a blackbox to me ... I think probably this might help in group by, having, where, etc. ... it might also help in parallel execution of proceedures and functions which are coded in java and hence developers can write them to take advantage of parallelism ... derby in embeddd mode will benefit hugely especially if it is deployed on desktop laptop netbook class machine which are fairly low on computing power but usually are at least dual core ... yes smp/multicore parallel execution has some overheads but parallelism will allow embeded derby to be used for more intensive oltp as well as olap complicated queries even though inherently derby does not support olap out of the box ... but a developer can write complicated queries subqueries aggregate queries corelated subqueries and use functions to output the results ... if certain derby finctionality can use parallelism ... similarly ... for network server it will be even better and derby can be used on even complex oltp or olap deployments ... again due to parallelism > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546775#comment-14546775 ] Bryan Pendleton commented on DERBY-6809: What particular features of Java 8 do you think would be beneficial to Derby? > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
