Re: Python thin client
Hi Stepan, Re your performance questions. Firstly, please pull out the latest sources from the ignite-7782 branch as it has some performance optimizations recently implemented. Secondly, Hotspot is a pretty advanced dynamic adaptive compiler and it's not fair to compare it to a purely interpreted Python language implementation. To get comparable results, please run your Java benchmark with -Djava.compiler=NONE. It turns the dynamic compiler off at runtime. I just did this exercise myself and got comparable scores. Please let me know if you still see any significant difference with the flag set. Thanks, P. On Fri, Oct 12, 2018 at 10:02 AM Dmitry Melnichuk < dmitry.melnic...@nobitlost.com> wrote: > Igor, > > I fixed my files. > > Dmitry > > On 10/13/18 12:14 AM, Igor Sapego wrote: > > Dmitry, > > > > I've run the tests and it appears that there are a lot of files without > > Apache > > licenses in Python client: [1] (See Unapproved licenses list). > > > > Can you either add headers or exclude file from the check, if you can not > > add one? I.e. to this list: [2] > > > > [1] - > > > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_LicensesHeaders/2069024:id/rat.zip%21/target/rat.txt > > [2] - https://github.com/apache/ignite/blob/master/parent/pom.xml#L817 > > > > Best Regards, > > Igor > > > > > > On Thu, Oct 11, 2018 at 1:13 PM Igor Sapego wrote: > > > >> Ok, I've filed a ticket [1] for the performance investigation and > targeted > >> it to 2.8. Feel free to assign it to yourself. > >> > >> I'm going to merge the ticket to master and ignite-2.7 branches by the > >> end of the week, if no one have any objections. > >> > >> [1] - https://issues.apache.org/jira/browse/IGNITE-9850 > >> > >> Best Regards, > >> Igor > >> > >> > >> On Thu, Oct 11, 2018 at 12:18 PM Dmitry Melnichuk < > >> dmitry.melnic...@nobitlost.com> wrote: > >> > >>> Stepan, > >>> > >>> Thank you for answering my question and for the updated results. > >>> > >>> I have ran the profiler (cProfile) against the benchmark code you > >>> provided and have not found any particular bottleneck. One cycle took > me > >>> 434 μs, which is the same order of magnitude as your result. > >>> > >>> I will need more time to analyze the performance of my client and find > a > >>> way to improve it. But is it a real stopper/blocker for the client > >>> itself? If there are no other issues, may we merge and release the > >>> client? Plus submit a jira-improvement to further investigate the > >>> performance of the Python platform. > >>> > >>> Dmitry > >>> > >>> On 10/11/18 4:19 PM, Степан Пильщиков wrote: > Dmitry, > > pip install -e from latest sources > > On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk, < > >>> dmitry.melnic...@nobitlost.com> > wrote: > > > Stepan! > > > > Please tell me one thing about how you created the environment for > your > > benchmarks, namely: how did you install the Python client. Did you > just > > do `pip install pyignite`, or did you pull my working branch from the > > downstream repository and did `pip install -e > > ignite/modules/platforms/python`? > > > > I highly recommend the latter, because PyPI version do not yet > include > > the latest improvements I did thanks to Dmitriy “qvad” Sherstobitov. > > These improvements can have a noticeable positive effect on speed. > > > > Dmitry > > > > On 10/10/18 11:06 PM, Степан Пильщиков wrote: > >> Dmitry, > >> > >> Thanks for review > >> > >> Agree with all suggestions. > >> > >> Made and run new benches without any redundant operations (prints, > >>> time > >> calculation), only with "put" in "while true" cycle (almost) > >> Case description, environment, results and code in ticket > >> https://issues.apache.org/jira/browse/IGNITE-9824 (last comment) > >> > >> Please review new metrics > >> Because picture is not changed so much, python still have > performance > > issues > >> > > > > >>> > >>> > > > >
[MTCGA]: new failures in builds [2071987] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *Recently contributed test failed in master WalRolloverTypesTest.testNextSegmentTypeWithCacheActivityFsyncModeArchiveOff https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6452593371537268368=%3Cdefault%3E=testDetails *Recently contributed test failed in master WalRolloverTypesTest.testCurrentSegmentTypeLogFsyncModeArchiveOff https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5660033795365972386=%3Cdefault%3E=testDetails *Recently contributed test failed in master WalRolloverTypesTest.testNextSegmentTypeFsyncModeArchiveOff https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8082082241133168626=%3Cdefault%3E=testDetails *Recently contributed test failed in master WalRolloverTypesTest.testCurrentSegmentTypeWithCacheActivityFsyncModeArchiveOff https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8292753159242959592=%3Cdefault%3E=testDetails Changes may lead to failure were done by - stkuzma http://ci.ignite.apache.org/viewModification.html?modId=834995=false - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 02:55:40 13-10-2018
[MTCGA]: new failures in builds [2071983] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *Recently contributed test failed in master WalRolloverTypesTest.testCurrentSegmentTypeWithCacheActivityFsyncModeArchiveOff https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4155161599708115903=%3Cdefault%3E=testDetails *Recently contributed test failed in master WalRolloverTypesTest.testNextSegmentTypeFsyncModeArchiveOff https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6936451271744559177=%3Cdefault%3E=testDetails *Recently contributed test failed in master WalRolloverTypesTest.testNextSegmentTypeWithCacheActivityFsyncModeArchiveOff https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8132318628533961125=%3Cdefault%3E=testDetails *Recently contributed test failed in master WalRolloverTypesTest.testCurrentSegmentTypeLogFsyncModeArchiveOff https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6059223584275515173=%3Cdefault%3E=testDetails Changes may lead to failure were done by - stkuzma http://ci.ignite.apache.org/viewModification.html?modId=834995=false - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 02:10:44 13-10-2018
Escalation guide for issues at the ASF
Hi all, An escalation guide for Apache issues was recently posted on d...@community.apache.org. I wanted to make sure our community was aware of this as well: https://www.apache.org/board/escalation In general, I invite you to discuss problems you see with the Ignite project/PMCs/PMC Chair. A discussion should be done openly, on the dev@ignite.apache.org list, or, in some cases, priv...@ignite.apache.org. Addressing issues early and publicly will keep most points from becoming too large to handle. Best Regards, Dmitriy Pavlov -- Forwarded message - From: Shane Curcuru Date: ср, 10 окт. 2018 г. в 0:50 Subject: [REVIEW] Escalation guide for issues at the ASF To: Apache ComDev I've written a guide for effective ways to escalate issues at the ASF that I hope is helpful for anytime there are issues that anyone may feel aren't being addressed within a specific project or mailing list: https://www.apache.org/board/escalation Having read many Apache lists for years now, I've come to understand the difficulties in discussing contentious issues - especially when we're discussing or raising them *across* communities. Every Apache project has their own communication style; many private mailing lists like the board and members lists also have their own styles. When individuals raise issues across these communities - from a project to board@ or from anywhere to members@ - all too often there is extra communication friction in the *way* the concern was brought from one list to the other - separate from the actual issue at question itself. I'm looking for some feedback and potential patches to ensure this is a helpful guide for effective escalations, and then I plan to include links to this in a broader email in the months to come. I've already incorporated a few fixes from some Members, but since this is deserved to serve all of our communities, I'm hoping for some broader feedback. We're all volunteers, and we each participate in many different communities. Ensuring we take the time to be clear, specific, and neutral in how we raise issues across groups helps everyone participate. Thanks, -- - Shane Vice Chairman The Apache Software Foundation - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[GitHub] ignite pull request #4978: Ignite-2.5.1-p14-hotfix-pme-revert
GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/4978 Ignite-2.5.1-p14-hotfix-pme-revert You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p14-hotfix-pme-revert Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4978.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4978 commit 6956097ceedd2e3e9edcb627d97e49afb7f0a26d Author: Pavel Kovalenko Date: 2018-06-06T12:24:39Z IGNITE-8482 Skip 2-phase partition release wait in case of activation or dynamic caches start - Fixes #4078. Signed-off-by: Alexey Goncharuk (cherry picked from commit 7c565d2) commit d777c76eadd0a2ccc50f1031c42626b135da5906 Author: Dmitriy Govorukhin Date: 2018-06-06T14:20:18Z IGNITE-8685 Fixed switch segment record size - Fixes #4130. Signed-off-by: Alexey Goncharuk (cherry picked from commit 2a048bd) commit ef4782d8a60eea870b43933480f2c9695c9fc55d Author: Alexey Goncharuk Date: 2018-06-07T11:55:13Z IGNITE-8706 Fixed testMemoryUsageMultipleNodes commit 6902383e01ee69d7efff9613a68f3fc419152305 Author: Pavel Kovalenko Date: 2018-05-14T10:14:52Z IGNITE-8422 Tests fix for Zookeeper discovery split brain detection shouldn't consider client nodes - Fixes #3975. Signed-off-by: dpavlov (cherry-picked from commit #19cbf8058b48a1f8fec60f7ceac70229e7c5391a) commit 6eef070f8e0627e2986d870cc09ceb9cb351ee0d Author: Sergey Chugunov Date: 2018-05-14T17:09:33Z IGNITE-8487 tmpfs is employed by ZooKeeper tests - Fixes #3994. Signed-off-by: dpavlov (cherry-picked from commit #67be050a2c7b9efdef2388c579fc060c68ff8a38) commit c9b82cc632ad1cac51661f729f8605ab6c97c1dd Author: Anton Kalashnikov Date: 2018-06-08T15:24:09Z IGNITE-8739 Implemented WA for tcp communication SPI hanging on descriptor reservation - Fixes #4148. Signed-off-by: Alexey Goncharuk (cherry picked from commit 7021651) commit 45953256ef0f09fd5450f6f6c6967a539c5cd395 Author: Pavel Kovalenko Date: 2018-05-03T14:01:20Z IGNITE-8226 Improved logging - Fixes #3796. Signed-off-by: Alexey Goncharuk (cherry picked from commit 8dd9c5d61c86c831b490134c3cd21f2ed47758d2) commit 77d089d857876f1901ade5a017a92c9835e2976a Author: Sergey Kosarev Date: 2018-06-13T14:24:42Z IGNITE-8736 Add transaction label to CU.txString() method output - Fixes #4152. Signed-off-by: Alexey Goncharuk commit c3c80439945134867e28e8d2c6db5ef9295141b6 Author: Andrey Gura Date: 2018-06-09T13:37:49Z IGNITE-8751 Failure handler accordingly to segmentation policy should be invoked on node segmentation instead of configured failure handler commit d33fe100bc9fdbcb66754d43ec0199e44233190b Author: Andrey Gura Date: 2018-06-13T14:30:18Z IGNITE-8781 GridNioServer accepter threads should have different names commit d2c304ca415919f0933461dde92fdf354539529b Author: Aleksey Plekhanov Date: 2018-06-14T17:41:31Z IGNITE-8763 java.nio.file.AccessDeniedException is not handled with default failure handler Signed-off-by: Andrey Gura commit 2545a4d65ae9c0289c9f6faf9d2ee498375aa3c7 Author: Sergey Chugunov Date: 2018-06-15T08:31:33Z IGNITE-8657 Simultaneous start of multiple clients may lead to client start hang when exchange history size is too short - Fixes #4102. Signed-off-by: Alexey Goncharuk (cherry-picked from commit #2b928c702b2d6a7c1de8d1b3b0a1e0e65e653f21) commit f4511d921c34fc1fc048afaf3ec10307b0f3bea2 Author: Pavel Kovalenko Date: 2018-06-15T09:48:24Z IGNITE-8610 Fixed checkpoint record search for WAL delta rebalancing - Fixes #4090. Signed-off-by: Alexey Goncharuk (cherry picked from commit 10aa02a) commit 1a8e9fcafa3a6d53ab01901be798cc8957252fe6 Author: EdShangGG Date: 2018-06-15T16:35:00Z IGNITE-8610 Fix compilation (cherry picked from commit 55af7d1) commit 298ca37aea710e098d033fcc5750e408b4a07c24 Author: Ilya Lantukh Date: 2018-05-23T15:02:23Z IGNITE-7809 fixed stable failures of IgniteWalFlushDefaultSelfTest in Ignite PDS 2 & PDS 2 Direct IO, new tests were added. - Fixes #3569. Signed-off-by: dpavlov (cherry picked from commit fed2c02) commit 3a1645135cf474f5760319a3c2dd7712041cc6f4 Author: dpavlov Date: 2018-05-25T11:48:04Z IGNITE-7809 Corrected failure handler to avoid suite timeout (cherry picked from commit 0c3a7a6) commit 3c44891906171d0668fee02bc5c9e9b2d4c7b432 Author: dpavlov Date: 2018-06-06T18:09:25Z IGNITE-8727: Disabling failed tests (cherry picked from commit 095f564) commit db9ee3e14f02ccab4954c539cb40e1f8faf8b34b Author: Pavel Kovalenko Date:
[GitHub] ignite pull request #4762: IGNITE-9601 Writing rollover record to the end of...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4762 ---
[jira] [Created] (IGNITE-9874) SQL: Jdbc benchmarks should use all cluster nodes in the jdbc url
Pavel Kuznetsov created IGNITE-9874: --- Summary: SQL: Jdbc benchmarks should use all cluster nodes in the jdbc url Key: IGNITE-9874 URL: https://issues.apache.org/jira/browse/IGNITE-9874 Project: Ignite Issue Type: Improvement Reporter: Pavel Kuznetsov Assignee: Pavel Kuznetsov Currectly we use first host in the cluster that matches condition. We should use all cluster nodes in the jdbc url separated by "," see org.apache.ignite.yardstick.jdbc.AbstractJdbcBenchmark#findThinAddress -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] asfgit closed pull request #37: IGNITE-9869 Running builds not uploaded into prefetched builds collection
asfgit closed pull request #37: IGNITE-9869 Running builds not uploaded into prefetched builds collection URL: https://github.com/apache/ignite-teamcity-bot/pull/37 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: Python thin client
Igor, I fixed my files. Dmitry On 10/13/18 12:14 AM, Igor Sapego wrote: Dmitry, I've run the tests and it appears that there are a lot of files without Apache licenses in Python client: [1] (See Unapproved licenses list). Can you either add headers or exclude file from the check, if you can not add one? I.e. to this list: [2] [1] - https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_LicensesHeaders/2069024:id/rat.zip%21/target/rat.txt [2] - https://github.com/apache/ignite/blob/master/parent/pom.xml#L817 Best Regards, Igor On Thu, Oct 11, 2018 at 1:13 PM Igor Sapego wrote: Ok, I've filed a ticket [1] for the performance investigation and targeted it to 2.8. Feel free to assign it to yourself. I'm going to merge the ticket to master and ignite-2.7 branches by the end of the week, if no one have any objections. [1] - https://issues.apache.org/jira/browse/IGNITE-9850 Best Regards, Igor On Thu, Oct 11, 2018 at 12:18 PM Dmitry Melnichuk < dmitry.melnic...@nobitlost.com> wrote: Stepan, Thank you for answering my question and for the updated results. I have ran the profiler (cProfile) against the benchmark code you provided and have not found any particular bottleneck. One cycle took me 434 μs, which is the same order of magnitude as your result. I will need more time to analyze the performance of my client and find a way to improve it. But is it a real stopper/blocker for the client itself? If there are no other issues, may we merge and release the client? Plus submit a jira-improvement to further investigate the performance of the Python platform. Dmitry On 10/11/18 4:19 PM, Степан Пильщиков wrote: Dmitry, pip install -e from latest sources On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk, < dmitry.melnic...@nobitlost.com> wrote: Stepan! Please tell me one thing about how you created the environment for your benchmarks, namely: how did you install the Python client. Did you just do `pip install pyignite`, or did you pull my working branch from the downstream repository and did `pip install -e ignite/modules/platforms/python`? I highly recommend the latter, because PyPI version do not yet include the latest improvements I did thanks to Dmitriy “qvad” Sherstobitov. These improvements can have a noticeable positive effect on speed. Dmitry On 10/10/18 11:06 PM, Степан Пильщиков wrote: Dmitry, Thanks for review Agree with all suggestions. Made and run new benches without any redundant operations (prints, time calculation), only with "put" in "while true" cycle (almost) Case description, environment, results and code in ticket https://issues.apache.org/jira/browse/IGNITE-9824 (last comment) Please review new metrics Because picture is not changed so much, python still have performance issues
[GitHub] ignite pull request #4977: IGNITE-9858
GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/4977 IGNITE-9858 You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-9858 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4977.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4977 commit dab8e7afc309cdccfd717bf57f46d174e9d9d82a Author: pereslegin-pa Date: 2018-10-12T15:50:41Z IGNITE-9858 Test fix. ---
[GitHub] ignite pull request #4976: IGNITE-9557: Assert in case of explains of update...
GitHub user pavel-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4976 IGNITE-9557: Assert in case of explains of updates operations. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9557 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4976.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4976 commit c58911894be0581b799cc7012005d8930d49de06 Author: Pavel Kuznetsov Date: 2018-10-11T12:13:49Z ignite-9557: tests for EXPLAIN update queries. commit 74d30f9241ddc3a424a3fd589c8c32bf1d2448cb Author: Pavel Kuznetsov Date: 2018-10-12T14:25:01Z ignite-9557: Throw exception on EXPLAIN of update query. Added assertion that query is not a EXPLAIN of update operation: INSERT, UPDATE, DELETE or MERGE. In this case we throw IgniteSqlException with code of unsupported operation. ---
[GitHub] ignite pull request #4975: IGNITE-9868 Send refresh partitions message for a...
GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/4975 IGNITE-9868 Send refresh partitions message for all cache groups together. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9868 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4975.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4975 commit aa37f3180abc80622ca802db382d4c43bb5e0b0e Author: Sergey Antonov Date: 2018-10-12T14:12:44Z IGNITE-9868 Send refresh partitions message for all cache group together. commit 83bff5ff9cfa42bb9bd8ad6c535a9f58d23c8c7e Author: Sergey Antonov Date: 2018-10-12T14:13:24Z IGNITE-9868 Code style commit 237060b8c2024902bf504e051afb099118db239d Author: Sergey Antonov Date: 2018-10-12T14:24:34Z IGNITE-9868 made log message more informative. ---
Re: Python thin client
Dmitry, I've run the tests and it appears that there are a lot of files without Apache licenses in Python client: [1] (See Unapproved licenses list). Can you either add headers or exclude file from the check, if you can not add one? I.e. to this list: [2] [1] - https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_LicensesHeaders/2069024:id/rat.zip%21/target/rat.txt [2] - https://github.com/apache/ignite/blob/master/parent/pom.xml#L817 Best Regards, Igor On Thu, Oct 11, 2018 at 1:13 PM Igor Sapego wrote: > Ok, I've filed a ticket [1] for the performance investigation and targeted > it to 2.8. Feel free to assign it to yourself. > > I'm going to merge the ticket to master and ignite-2.7 branches by the > end of the week, if no one have any objections. > > [1] - https://issues.apache.org/jira/browse/IGNITE-9850 > > Best Regards, > Igor > > > On Thu, Oct 11, 2018 at 12:18 PM Dmitry Melnichuk < > dmitry.melnic...@nobitlost.com> wrote: > >> Stepan, >> >> Thank you for answering my question and for the updated results. >> >> I have ran the profiler (cProfile) against the benchmark code you >> provided and have not found any particular bottleneck. One cycle took me >> 434 μs, which is the same order of magnitude as your result. >> >> I will need more time to analyze the performance of my client and find a >> way to improve it. But is it a real stopper/blocker for the client >> itself? If there are no other issues, may we merge and release the >> client? Plus submit a jira-improvement to further investigate the >> performance of the Python platform. >> >> Dmitry >> >> On 10/11/18 4:19 PM, Степан Пильщиков wrote: >> > Dmitry, >> > >> > pip install -e from latest sources >> > >> > On Thu, 11 Oct 2018, 06:37 Dmitry Melnichuk, < >> dmitry.melnic...@nobitlost.com> >> > wrote: >> > >> >> Stepan! >> >> >> >> Please tell me one thing about how you created the environment for your >> >> benchmarks, namely: how did you install the Python client. Did you just >> >> do `pip install pyignite`, or did you pull my working branch from the >> >> downstream repository and did `pip install -e >> >> ignite/modules/platforms/python`? >> >> >> >> I highly recommend the latter, because PyPI version do not yet include >> >> the latest improvements I did thanks to Dmitriy “qvad” Sherstobitov. >> >> These improvements can have a noticeable positive effect on speed. >> >> >> >> Dmitry >> >> >> >> On 10/10/18 11:06 PM, Степан Пильщиков wrote: >> >>> Dmitry, >> >>> >> >>> Thanks for review >> >>> >> >>> Agree with all suggestions. >> >>> >> >>> Made and run new benches without any redundant operations (prints, >> time >> >>> calculation), only with "put" in "while true" cycle (almost) >> >>> Case description, environment, results and code in ticket >> >>> https://issues.apache.org/jira/browse/IGNITE-9824 (last comment) >> >>> >> >>> Please review new metrics >> >>> Because picture is not changed so much, python still have performance >> >> issues >> >>> >> >> >> > >> >>
[jira] [Created] (IGNITE-9873) SQL: MERGE requires column names specified explicitly
Pavel Kuznetsov created IGNITE-9873:
---
Summary: SQL: MERGE requires column names specified explicitly
Key: IGNITE-9873
URL: https://issues.apache.org/jira/browse/IGNITE-9873
Project: Ignite
Issue Type: Bug
Reporter: Pavel Kuznetsov
Doc (https://apacheignite-sql.readme.io/docs/merge) defines MEGE operator:
{noformat}
MERGE INTO tableName [(columnName [,...])]
[KEY (columnName [,...])]
{VALUES {({ DEFAULT | expression } [,...])} [,...] | select}
{noformat}
So square brackets tell us columnName part can ben ommited. But in this case
we'll have parsing error.
How to reproduce:
execute sql script via any api.
{noformat}
CREATE TABLE TEST (ID LONG PRIMARY KEY, VAL LONG);
MERGE INTO TEST VALUES (1, 2);
{noformat}
But command below works well though:
{noformat}
MERGE INTO TEST (ID, VAL) VALUES (1, 2);
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9872) [Test falied] IgniteSinkConnectorTest.testSinkPutsWithoutTransformation
Maxim Pudov created IGNITE-9872:
---
Summary: [Test falied]
IgniteSinkConnectorTest.testSinkPutsWithoutTransformation
Key: IGNITE-9872
URL: https://issues.apache.org/jira/browse/IGNITE-9872
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Maxim Pudov
Fix For: 2.8
Test started failing after updating kafka
https://issues.apache.org/jira/browse/IGNITE-9126
There is an issue with classloading in kafka
https://issues.apache.org/jira/browse/KAFKA-6914, which was fixed but wasn't
included to any public releases yet.
It can be fixed in our test by replacing system class loader in
org.apache.ignite.stream.kafka.connect.IgniteSinkConnectorTest#beforeTest:
Field scl = ClassLoader.class.getDeclaredField("scl"); // Get system class
loader
scl.setAccessible(true); // Set accessible
scl.set(null, getClass().getClassLoader());
However, it might be better to wait for kafka 1.1.2 and just update its version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] dspavlov opened a new pull request #37: IGNITE-9869 Running builds not uploaded into prefetched builds collection
dspavlov opened a new pull request #37: IGNITE-9869 Running builds not uploaded into prefetched builds collection URL: https://github.com/apache/ignite-teamcity-bot/pull/37 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (IGNITE-9871) IgniteOOM on client is not clear
Sergey Kozlov created IGNITE-9871: - Summary: IgniteOOM on client is not clear Key: IGNITE-9871 URL: https://issues.apache.org/jira/browse/IGNITE-9871 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.6 Reporter: Sergey Kozlov Fix For: 2.8 1. Start grid with small data region w/o PDS 2. Start client used streamer and load data exceeding the data region. 3. The client throws IgniteOOM but it's not clear which node caused the issue. Also the client may not expect such exception like this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4948: IGNITE-9606: JDBC getPrimaryKeys() returns wrong ...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4948 ---
[jira] [Created] (IGNITE-9870) GridDhtPartitionsFullMessage#prepareMarshal compression parallelization.
Stanilovsky Evgeny created IGNITE-9870: -- Summary: GridDhtPartitionsFullMessage#prepareMarshal compression parallelization. Key: IGNITE-9870 URL: https://issues.apache.org/jira/browse/IGNITE-9870 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.6 Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny In huge topologies ~ 200 cluster nodes , 100 caches , 32k partitions per cache, full map generation takes about 3 sec, seems correct approach here in parallelization. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9869) [TC Bot] Running builds not uploaded into prefetched builds collection
Dmitriy Pavlov created IGNITE-9869: -- Summary: [TC Bot] Running builds not uploaded into prefetched builds collection Key: IGNITE-9869 URL: https://issues.apache.org/jira/browse/IGNITE-9869 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov PR inspection page shows there are running builds, Reproduced during #2744 IGNITE-6444: Validate that copyOnRead flag is configured with on-heap cache enabled. build check. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9868) Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full Message creating
Sergey Antonov created IGNITE-9868: -- Summary: Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full Message creating Key: IGNITE-9868 URL: https://issues.apache.org/jira/browse/IGNITE-9868 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Assignee: Sergey Antonov Made messages more informative and, maybe, reduce number of messages in log file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9867) Add ability to block out of range IP on discovery request
ARomantsov created IGNITE-9867:
--
Summary: Add ability to block out of range IP on discovery request
Key: IGNITE-9867
URL: https://issues.apache.org/jira/browse/IGNITE-9867
Project: Ignite
Issue Type: Improvement
Components: general
Affects Versions: 2.7
Reporter: ARomantsov
Fix For: 2.8
Now we can set list of cluster collector node, but cannot deny another ips to
connect to our cluster
{code:java}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4974: IGNITE-8227 test failure handler
GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/4974 IGNITE-8227 test failure handler You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite IGNITE-8227 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4974.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4974 commit d4bc2199d6ebd72be328386ecadd0f900ad3b0a0 Author: Dmitrii Ryabov Date: 2018-10-12T09:58:13Z IGNITE-8227 test failure handler ---
[jira] [Created] (IGNITE-9866) Unify and optimise *.sh and *.bat code base
Peter Ivanov created IGNITE-9866: Summary: Unify and optimise *.sh and *.bat code base Key: IGNITE-9866 URL: https://issues.apache.org/jira/browse/IGNITE-9866 Project: Ignite Issue Type: Improvement Affects Versions: 2.7 Reporter: Peter Ivanov Assignee: Peter Ivanov Fix For: 2.8 There are lots of duplicated code at /bin/*.[sh|bat] scripts (especially -- Java run string construction). It is required to move duplicated code to common function script. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4973: IGNITE-9864: fix .net query SQL tests
GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/4973 IGNITE-9864: fix .net query SQL tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9864 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4973.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4973 commit 140631f17f68fd6846fe853cb19e4d002a3fc976 Author: tledkov-gridgain Date: 2018-10-12T09:50:46Z IGNITE-9864: fix .net query SQL tests ---
[GitHub] ignite pull request #4971: Ignite 9612
GitHub user ascherbakoff opened a pull request: https://github.com/apache/ignite/pull/4971 Ignite 9612 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9612 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4971.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4971 commit 7e3c341ff4b99d3ca6f10283da539464d45a1c17 Author: ascherbakoff Date: 2018-09-23T16:34:09Z IGNITE-9612 wip. commit 5ab5553e989df5971472978d36515cfe1565627b Author: Aleksei Scherbakov Date: 2018-09-24T10:49:59Z IGNITE-9612 wip. commit 5ad45b70e1fe6a921b49aec943bec874dcf64758 Author: Aleksei Scherbakov Date: 2018-09-25T10:30:18Z IGNITE-9612 wip. commit 53c99ba9bb02cd83ee9752224ca27a82312b731d Author: Aleksei Scherbakov Date: 2018-09-25T10:33:15Z IGNITE-9612 wip. commit 795f296cfa7cd0783f03d76b1b7066b835a3d4c2 Author: Aleksei Scherbakov Date: 2018-09-25T10:33:34Z Merge branch 'master' of https://github.com/apache/ignite into ignite-9612 commit 9a5b1519c333953fb24621742ff0ad6aa03a011a Author: Aleksei Scherbakov Date: 2018-09-26T09:48:25Z Merge branch 'master' of https://github.com/apache/ignite into ignite-9612 commit b105f7beb8643ad971d33352b8fd3fd90e6bb3f4 Author: Aleksei Scherbakov Date: 2018-09-26T17:20:48Z IGNITE-9612 wip. commit db622f6f709d758324f15b6aa582c40c3bbea13d Author: ascherbakoff Date: 2018-09-27T19:28:57Z Merge branch 'master' of https://github.com/apache/ignite into ignite-9612 commit 12c36d2771e870c08e6bfc2d3eef561f9ac6c8ca Author: Aleksei Scherbakov Date: 2018-09-28T08:34:05Z Merge branch 'master' of https://github.com/apache/ignite into ignite-9612 commit a2c6b48127f9d1a4660c43e05b9302c7c16dc2d1 Author: Aleksei Scherbakov Date: 2018-09-28T08:36:38Z Merge branch 'ignite-9612' of https://github.com/gridgain/apache-ignite into ignite-9612 commit 0b2b24a58bcd0a9a6f35536852628ddde4bcb846 Author: Aleksei Scherbakov Date: 2018-09-28T09:04:57Z IGNITE-9612 wip. commit 29d74a5f3624d8493b22c67e388d154ad9b88951 Author: Aleksei Scherbakov Date: 2018-10-12T08:40:16Z Merge branch 'master' of https://github.com/apache/ignite into ignite-9612 commit 7eb673ddaf311fbcc00e3d3918689ccfe4a8a114 Author: Aleksei Scherbakov Date: 2018-10-12T09:45:35Z IGNITE-9612 Fix snapshot of empty group metadata. ---
[GitHub] ignite pull request #4972: IGNITE-9809 Web console: more minor fixes
GitHub user Klaster1 opened a pull request: https://github.com/apache/ignite/pull/4972 IGNITE-9809 Web console: more minor fixes 1. Update confirmation E2E selectors so these work when multiple modals are opened. 2. Update TestCafe to 0.22.0. 3. Update reduxDevtoolsIntegration.js so it doesn't crash when there's a Promise in action payload. 4. Fix form-field postfix position in browsers that don't support [place-self](https://developer.mozilla.org/en-US/docs/Web/CSS/place-self) (Edge and Safari). You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9809-2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4972.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4972 commit aa6ec6923e560c6242ee24853342c0359bdd118d Author: Ilya Borisov Date: 2018-10-12T09:45:14Z IGNITE-9809 Update TestCafe to 0.22.0. commit fd452c50d770007f0e3f6066917d2137a77f73f6 Author: Ilya Borisov Date: 2018-10-12T09:45:31Z IGNITE-9809 Update confirmation E2E selectors so these work when multiple modals are opened. commit 0da30dc7ebe350e38afed07a967f3f95fad64cfd Author: Ilya Borisov Date: 2018-10-12T09:45:50Z IGNITE-9809 Update reduxDevtoolsIntegration.js so it doesn't crash when there's a Promise in action payload. commit 3c83222df148e4ae0fe51aba1da2c28ce45118a3 Author: Ilya Borisov Date: 2018-10-12T09:46:12Z IGNITE-9809 Fix form-field postfix position in browsers that don't support place-self. ---
Re: hi folks
Hello there! Did you ask to be added to contributors list already? Regards, -- Ilya Kasnacheev чт, 11 окт. 2018 г. в 5:33, Floydz Kborgmann : > jus trying 2 understand the proj 4now.. hope i can help soon... ignite is > great! > cheers >
[GitHub] ignite pull request #4970: 9769 test flakiness
GitHub user SomeFire opened a pull request: https://github.com/apache/ignite/pull/4970 9769 test flakiness You can merge this pull request into a Git repository by running: $ git pull https://github.com/SomeFire/ignite 9769 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4970.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4970 commit b5e93cdb80b80e68c9c08a593f18a26fc814faac Author: Dmitrii Ryabov Date: 2018-10-12T09:02:27Z 9769 test flakiness ---
[GitHub] ignite pull request #4954: IGNITE-9749 MVCC: Assertion error in JdbcThinTran...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4954 ---
[jira] [Created] (IGNITE-9865) Javadoc failure on TDE
Peter Ivanov created IGNITE-9865:
Summary: Javadoc failure on TDE
Key: IGNITE-9865
URL: https://issues.apache.org/jira/browse/IGNITE-9865
Project: Ignite
Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Nikolay Izhikov
After IGNITE-8485 there is Javadoc failure running {{mvn initialise -Pjavadoc}}:
{code}
[10:44:52] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException
has occured: Execution failed due to: 'Other Packages' section should not be
present, all packages should have corresponding documentation groups:
/data/teamcity/work/9198da4c51c3e112/target/javadoc/core/overview-summary.html;Please
add packages description to parent/pom.xml into (maven-javadoc-plugin)
/ /
[10:44:52] [ERROR]
[10:44:52] [ERROR] around Ant part .. @ 11:51 in
/data/teamcity/work/9198da4c51c3e112/target/antrun/build-main.xml
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4958: Added IgniteDataTransferObject and deprecated Vis...
Github user akuznetsov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/4958 ---
[GitHub] ignite pull request #4969: IGNITE-9837
GitHub user NSAmelchev opened a pull request: https://github.com/apache/ignite/pull/4969 IGNITE-9837 Fix for IGNITE-9837. See description for details. You can merge this pull request into a Git repository by running: $ git pull https://github.com/NSAmelchev/ignite ignite-9837 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4969.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4969 commit 2f0bc2f3796a3610cc2858f18a463c4196b01ff8 Author: NSAmelchev Date: 2018-10-12T08:19:17Z Fix BinaryMetadataUpdatesFlowTest tests. ---
[jira] [Created] (IGNITE-9864) CacheQueriesTest test fails in .NET
Vladimir Ozerov created IGNITE-9864: --- Summary: CacheQueriesTest test fails in .NET Key: IGNITE-9864 URL: https://issues.apache.org/jira/browse/IGNITE-9864 Project: Ignite Issue Type: Task Components: platforms Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4968: IGNITE-9738 Client node can suddenly fail on star...
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4968 IGNITE-9738 Client node can suddenly fail on start You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9738 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4968.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4968 commit 2544f2a6e76d80b200131821343e469345a4ca6d Author: vd-pyatkov Date: 2018-10-12T07:59:18Z IGNITE-9738 Client node can suddenly fail on start ---
[MTCGA]: new failures in builds [2063714, 2060437] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New test failure in master CacheQueriesTest.TestSqlQueryTimeout https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1799006078426517905=%3Cdefault%3E=testDetails *New test failure in master CacheQueriesTest.TestSqlQueryTimeout https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=652595258658009887=%3Cdefault%3E=testDetails *New test failure in master CacheQueriesTest.TestSqlFieldsQueryTimeout https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1608154422011714086=%3Cdefault%3E=testDetails *New test failure in master CacheQueriesTest.TestSqlFieldsQueryTimeout https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7501074628762401186=%3Cdefault%3E=testDetails Changes may lead to failure were done by - jokserfn http://ci.ignite.apache.org/viewModification.html?modId=834843=false - aplatonovv http://ci.ignite.apache.org/viewModification.html?modId=834837=false - kondakov87 http://ci.ignite.apache.org/viewModification.html?modId=834798=false - mr.weider http://ci.ignite.apache.org/viewModification.html?modId=834773=false - tledkov http://ci.ignite.apache.org/viewModification.html?modId=834768=false *New stable failure of a flaky test in master CacheQueriesTestSimpleName.TestSqlQueryTimeout https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5152015653430321503=%3Cdefault%3E=testDetails *New stable failure of a flaky test in master CacheQueriesTest.TestSqlQueryTimeout https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4876568478269605522=%3Cdefault%3E=testDetails *New stable failure of a flaky test in master CacheQueriesTest.TestSqlFieldsQueryTimeout https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4556345115781719312=%3Cdefault%3E=testDetails *New stable failure of a flaky test in master CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-833328613447734863=%3Cdefault%3E=testDetails Changes may lead to failure were done by - kondakov87 http://ci.ignite.apache.org/viewModification.html?modId=834798=false - mr.weider http://ci.ignite.apache.org/viewModification.html?modId=834773=false - tledkov http://ci.ignite.apache.org/viewModification.html?modId=834768=false - isapego http://ci.ignite.apache.org/viewModification.html?modId=834760=false - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 10:10:36 12-10-2018
[jira] [Created] (IGNITE-9863) Refactor VisorDataTransferObject to common class
Alexey Kuznetsov created IGNITE-9863: Summary: Refactor VisorDataTransferObject to common class Key: IGNITE-9863 URL: https://issues.apache.org/jira/browse/IGNITE-9863 Project: Ignite Issue Type: Task Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov Initially VisorDataTransferObject was implemented to use with Visor CMD only. But I see that now it is using together with control.sh utility. And it looks strange that some classes not related to Visor use some Visor-specific class. Lets move this class to "org.apache.ignite.internal.dto" package with name IgniteDataTransferObject and deprecate VisorDataTransferObject (with removal in 3.0). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4967: Ignite 9272 my
GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/4967 Ignite 9272 my You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-9272-my Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4967.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4967 commit ad9b4a27a3e459cc0fd9a380839a93cdf05f09d2 Author: Nikolay Izhikov Date: 2018-10-12T06:04:40Z IGNITE-9272: Fast crc commit c85301017fc4d80a38186b50e4699c61326f3134 Author: Nikolay Izhikov Date: 2018-10-12T06:07:46Z IGNITE-9272: improvements commit 3b810afeb29a4555e207534b493f09b6afc31f8b Author: Nikolay Izhikov Date: 2018-10-12T06:12:48Z IGNITE-9272: Improvements. commit 67261cf7c1c7766d0ad4c4998a68c3e30f3ec51f Author: Nikolay Izhikov Date: 2018-10-12T06:18:10Z IGNITE-9272: Improvements. ---
