[MTCGA]: new failures in builds [5838760] 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-nightly ThickExamplesExternalNodeTest.TestThickExampleWithExternalNode(Task) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6284027455125641283=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesExternalNodeTest.TestThickExampleWithExternalNode(PeerAssemblyLoading) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-247017066118723824=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesTest.TestThickExample(Linq) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7506567733549254534=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesTest.TestThickExample(BinaryMode) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8998437437990744289=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThinExamplesTest.TestThinExample(SqlThin) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8967725938765676740=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThinExamplesTest.TestThinExample(DdlThin) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2494824099260932765=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThinExamplesTest.TestThinExample(QueryScanThin) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6468797212677727177=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesExternalNodeTest.TestThickExampleWithExternalNode(Dml) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7626155299713721125=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThinExamplesTest.TestThinExample(QueryContinuousThin) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4752428134168076489=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesTest.TestThickExample(PutGet) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6603068568013112746=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesTest.TestThickExample(MultiTieredCache) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7475862472472842255=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesExternalNodeTest.TestThickExampleWithExternalNode(Func) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1513721878440053771=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThinExamplesTest.TestThinExample(OptimisticTransactionThin) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6509612185650743702=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesExternalNodeTest.TestThickExampleWithExternalNode(Store) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2832985891446251365=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesExternalNodeTest.TestThickExampleWithExternalNode(AtomicReference) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=268958979301630=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesTest.TestThickExample(Ddl) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2248018306087225518=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesTest.TestThickExample(AtomicSequence) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5657039661552089646=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesExternalNodeTest.TestThickExampleWithExternalNode(Lifecycle) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3378169314970688724=%3Cdefault%3E=testDetails *Recently contributed test failed in master-nightly ThickExamplesExternalNodeTest.TestThickExampleWithExternalNode(PutGet) https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5815713929294899441=%3Cdefault%3E=testDetails *Recently contributed test failed in
Re: [Discussion] Kanban board for quick start issues to join the community
I guess the same result could be achieved with simple labels, no? With regards, Cos On 22.01.2021 16:25, Saikat Maitra wrote: Hi, I was looking into our community page to find new open issues that I can contribute to and the easy and moderate tickets, tickets for beginners and SQL tasks help me to find open issues to contribute. I am also thinking if we should use a project Kanban board in jira and move these issues in the ToDo column so that it is easy to find and contribute to these open issues. I have seen few Apache Project like Beam, Flink already uses Kanban board https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=BEAM=325 https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=356=FLINK Please review and let me know your thoughts. Regards Saikat
Re: Contribution to Apache
Hello Igor, Welcome to the community! Hope you enjoy the contribution process and grow your expertise in both Ignite and distributed databases. I've added you to the contributors' list. So, go ahead and take over the ticket. - Denis On Fri, Jan 22, 2021 at 10:19 AM Игорь Барышников wrote: > Hello everyone! > > My name is Igor Baryshnikov and I am a Java developer with four years of > industry experience. I use Apache products from time to time so I thought > it would be nice to contribute to the community. > > I would like to start with something simple like IGNITE-12724, so kindly > ask you to give me the necessary rights to interact with Ignite's JIRA. My > profile is [1]. > > Best, > Igor > > [1] https://issues.apache.org/jira/secure/ViewProfile.jspa?name=igorb >
Re: Start contributing
Hello Alexey, Welcome aboard! You're in, I've added you to JIRA contributor's list. Look forward to your contribution! - Denis On Fri, Jan 22, 2021 at 12:46 AM Алексей wrote: > > Hi guys! > > My name is Alexey Plotnik, I'm a software engineer. > > I'd like to start contributing to Apache Ignite project. > > Could you please give me access to Apache Ignite jira, my nickname is > alexey.plotnik > > Thank you! >
[MTCGA]: new failures in builds [5837597] 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 org.apache.ignite.scalar.testsuites.ScalarExamplesSelfTestSuite: org.apache.ignite.scalar.testsuites.ScalarExamplesSelfTestSuite. https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1604878018597183817=%3Cdefault%3E=testDetails Changes may lead to failure were done by - sergey chugunov https://ci.ignite.apache.org/viewModification.html?modId=914853 - maksim timonin https://ci.ignite.apache.org/viewModification.html?modId=914993 - 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 00:59:51 23-01-2021
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Nikita, thanks. I reviewed those and shared some suggestions. Please take them into consideration. - Denis On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов wrote: > Hi everyone, > > The following documentation tasks for the important features now have PATCH > AVAILABLE status: > >- Caches warming up strategy - >https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro >- Update on JMX default configuration removal - >https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro >- Control.sh indexes manipulation commands - >https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro > > Please see the PR's attached to the tickets. > > Thank you! > > Regards, > Nikita > > пт, 22 янв. 2021 г. в 18:03, shm : > > > Hi All, > > Can you please also include a critical ticket > > https://issues.apache.org/jira/browse/IGNITE-13912 > > to 2.10 In terms of functionality it is a blocker. Still some debugging > is > > going on related to this issue. > > > > Thanks, > > Shiva > > > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Hi everyone, The following documentation tasks for the important features now have PATCH AVAILABLE status: - Caches warming up strategy - https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro - Update on JMX default configuration removal - https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro - Control.sh indexes manipulation commands - https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro Please see the PR's attached to the tickets. Thank you! Regards, Nikita пт, 22 янв. 2021 г. в 18:03, shm : > Hi All, > Can you please also include a critical ticket > https://issues.apache.org/jira/browse/IGNITE-13912 > to 2.10 In terms of functionality it is a blocker. Still some debugging is > going on related to this issue. > > Thanks, > Shiva > > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
[Discussion] Kanban board for quick start issues to join the community
Hi, I was looking into our community page to find new open issues that I can contribute to and the easy and moderate tickets, tickets for beginners and SQL tasks help me to find open issues to contribute. I am also thinking if we should use a project Kanban board in jira and move these issues in the ToDo column so that it is easy to find and contribute to these open issues. I have seen few Apache Project like Beam, Flink already uses Kanban board https://issues.apache.org/jira/secure/RapidBoard.jspa?projectKey=BEAM=325 https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=356=FLINK Please review and let me know your thoughts. Regards Saikat
Contribution to Apache
Hello everyone! My name is Igor Baryshnikov and I am a Java developer with four years of industry experience. I use Apache products from time to time so I thought it would be nice to contribute to the community. I would like to start with something simple like IGNITE-12724, so kindly ask you to give me the necessary rights to interact with Ignite's JIRA. My profile is [1]. Best, Igor [1] https://issues.apache.org/jira/secure/ViewProfile.jspa?name=igorb
Re: WAL enable/disable does not work on unstable topology - removal or warning
Hello! I have created a separate ticket for that work: https://issues.apache.org/jira/browse/IGNITE-14039 I have designated it as a blocker for 2.10 I have submitted a pull request. I will run tests: https://github.com/apache/ignite/pull/8688/files Mikhail, your approach makes sense. However, I don't think we can change existing API - too late for that, we have to maintain compatibility. Regards, -- Ilya Kasnacheev чт, 21 янв. 2021 г. в 15:33, Maxim Muzafarov : > Ilya, > > This issue must be fixed for sure (don't think we should rewrite it > from scratch). > > Let's add TODO and warning comment referencing to this issue to the > JavaDoc and also add the same warning to documentation pages. The > reference to the issue will allow users to track the fixing progress. > > > On Wed, 20 Jan 2021 at 22:39, Mikhail Cherkasov > wrote: > > > > Hi Ilya, > > > > WAL disable is a very powerful feature that is widely adopted by users. > > For sure we need to fix it, even if it means rewriting it. > > The warning makes sense, in this case, we can even reduce the priority of > > the issue, but anyway, it's at least a critical one, because it can lead > to > > data loss(and it does). > > I would say, instead of a warning, we can do something more noticeable, > > like method signature change like: > > boolean disableWal(String cacheName, boolean > > iReadJavaDockAndAwareOfTheRisk); - this one definitely will be noticed. > > > > Thanks, > > Mike. > > > > On Wed, Jan 20, 2021 at 8:28 AM Ilya Kasnacheev > wrote: > > > > > Hello! > > > > > > We had this feature for a few versions, where you could do > gnite.cluster(). > > > disableWal() to temporarily disable WAL on a specific cache, involving > a > > > PME and checkpoint on every node. > > > > > > However, it became apparent that you cannot enable or disable WAL on > any > > > kind of unstable topology, at all: > > > https://issues.apache.org/jira/browse/IGNITE-13976 > > > > > > You cannot even disable WAL while a baseline node is offline: When it > comes > > > back, it will not sync its WAL enabled status with the rest of the > cluster, > > > and all subsequent "WAL enable" or "WAL disable" operations will fail > on > > > that cache, with no clear way to recover this cache: > > > > > > ignite.close(); > > > client.cluster().disableWal(CACHE_NAME); > > > nodes.add(Ignition.start(igniteCfg(false, consistentId))); > > > client.cluster().enableWal(CACHE_NAME); // will fail > > > > > > Even if this simple scenario is fixed, it seems that there are multiple > > > failure scenarios if you try to add or remove a node in the middle of > WAL > > > state change operation. It does not seem that we have any expertise in > wal > > > disable/enable implementation right now, and I did not find a simple > way of > > > fixing it short of a full rewrite. > > > > > > Therefore, I propose that we should *(a) disable that feature* in 2.10 > or* > > > (b) give a clear warning *when it is used, and also mention in the > > > documentation that it may only be used on stable topology. > > > > > > We may also want to re-mark this feature's API as @IgniteExperimental. > > > I have lifted this ticket to be a Blocker. > > > > > > WDYT? > > > > > > Regards, > > > > > > > > > -- > > Thanks, > > Mikhail. >
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Hi All, Can you please also include a critical ticket https://issues.apache.org/jira/browse/IGNITE-13912 to 2.10 In terms of functionality it is a blocker. Still some debugging is going on related to this issue. Thanks, Shiva -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)
Hi everyone, I'm finishing my work on the documentation tasks for the following important features: - Caches warming up strategy - https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro - Update on JMX default configuration removal - https://issues.apache.org/jira/browse/IGNITE-13606?src=confmacro - Control.sh indexes manipulation commands - https://issues.apache.org/jira/browse/IGNITE-13285?src=confmacro I will provide PR's to these and some other features a bit later today. Please be ready to review the latest changes. Thank you! Regards, Nikita чт, 21 янв. 2021 г. в 22:09, Maxim Muzafarov : > Folks, > > > This is the list of bugs which I've cherry-picked to the ignite-2.10 > branch: > > > Starvation in mgmt pool caused by MetadataTask execution > https://issues.apache.org/jira/browse/IGNITE-13960 > > .NET: LINQ provider emits incorrect table alias for queries with JOIN > and GROUP BY combined > https://issues.apache.org/jira/browse/IGNITE-13754 > > Query cancellation freezes on local lazy queries > https://issues.apache.org/jira/browse/IGNITE-13964 > > SQL: REPLICATED cache cannot be left-joined to PARTITIONED > https://issues.apache.org/jira/browse/IGNITE-8732 > > .NET: logger throws KeyNotFound on creating cache with nullable 'sbyte?' > field > https://issues.apache.org/jira/browse/IGNITE-12090 > > Possible deadlock between methods from GridEncryptionManager > https://issues.apache.org/jira/browse/IGNITE-13906 > > OOM on creating rebalance iterator while rebalancing cache with large > values. > https://issues.apache.org/jira/browse/IGNITE-14003 > > On Mon, 18 Jan 2021 at 17:20, Pavel Tupitsyn wrote: > > > > Maxim, > > > > No objections for .NET-related cherry-picks. > > > > Thank you! > > > > On Mon, Jan 18, 2021 at 4:52 PM Никита Сафонов < > vlasovpavel2...@gmail.com> > > wrote: > > > > > Hi Maxim et al, > > > > > > Thank you very much! > > > I do appreciate your help! > > > > > > Regards, > > > Nikita > > > > > > пн, 18 янв. 2021 г. в 16:16, Maxim Muzafarov : > > > > > > > Folks, > > > > > > > > I'd like to cherry-pick these bugs to the ignite-2.10 branch. > > > > Do you have any objections? > > > > > > > > > > > > Starvation in mgmt pool caused by MetadataTask execution > > > > https://issues.apache.org/jira/browse/IGNITE-13960 > > > > > > > > .NET: LINQ provider emits incorrect table alias for queries with JOIN > > > > and GROUP BY combined > > > > https://issues.apache.org/jira/browse/IGNITE-13754 > > > > > > > > Query cancellation freezes on local lazy queries > > > > https://issues.apache.org/jira/browse/IGNITE-13964 > > > > > > > > SQL: REPLICATED cache cannot be left-joined to PARTITIONED > > > > https://issues.apache.org/jira/browse/IGNITE-8732 > > > > > > > > .NET: logger throws KeyNotFound on creating cache with nullable > 'sbyte?' > > > > field > > > > https://issues.apache.org/jira/browse/IGNITE-12090 > > > > > > > > Possible deadlock between methods from GridEncryptionManager > > > > https://issues.apache.org/jira/browse/IGNITE-13906 > > > > > > > > On Mon, 18 Jan 2021 at 11:05, Maxim Muzafarov > wrote: > > > > > > > > > > Nikita, > > > > > > > > > > Thank you for sharing the progress. I will check all the PRs you > > > > > reviewed and merge them if need. I will help you with the *[list > #3]* > > > > > issues (some of them already complete and merged to the 2.10 > branch). > > > > > > > > > > On Fri, 15 Jan 2021 at 22:43, Никита Сафонов < > > > vlasovpavel2...@gmail.com> > > > > wrote: > > > > > > > > > > > > Hi Maxim et al, > > > > > > > > > > > > > > > > > > I’d like to share my interim status on Ignite 2.10 documentation > > > work. > > > > > > > > > > > > > > > > > > > > > > > >- The following PR’s *[list #1]* are reviewed and, when the > > > > changes are > > > > > >accepted, ready to be merged, including 4 important features. > > > > > > > > > > > > > > > > > > > > > > > >- I’m pretty sure that I’ll collect and put together > information > > > for > > > > > >most of the following tasks *[list #2] *by the end of the next > > > week, > > > > > >including 3 important features. > > > > > > > > > > > > > > > > > > > > > > > >- I’d kindly ask your help with the following items *[list > #3]*, > > > > > >including 2 important features. > > > > > > > > > > > > > > > > > > So, for the sake of documentation completeness, I suggest > finalizing > > > > our > > > > > > doc work next week. > > > > > > > > > > > > Regards, > > > > > > Nikita > > > > > > > > > > > > > > > > > > *[list #1]:* > > > > > > > > > > > > > > > > > > * IGNITE-13968 Add snapshot events documentation pages > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-13968 > > > > > > > > > > > > https://github.com/apache/ignite/pull/8642 > > > > > > > > > > > > > > > > > > > > > > > > * Add documentation for new checkpoint, cluster and cache metrics > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-13982 > > > > > > > > > > >
[jira] [Created] (IGNITE-14039) Add warnings about WAL enable/disable requiring topology stability
Ilya Kasnacheev created IGNITE-14039: Summary: Add warnings about WAL enable/disable requiring topology stability Key: IGNITE-14039 URL: https://issues.apache.org/jira/browse/IGNITE-14039 Project: Ignite Issue Type: Bug Components: documentation Affects Versions: 2.9.1 Reporter: Ilya Kasnacheev Assignee: Ilya Kasnacheev Fix For: 2.10 Due to IGNITE-13976 WAL enable/disable is not suitable for any kind of changing topology and will cause cache to go into inconsistent state. We need to add warnings to javadoc, runtime and documentation, and provide tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] Python thin client development approach.
Igor, I've never talked about complete removal of TC builds. I just suggested to add TC jobs for different python versions and use travis heavily. Currently, we have done most of the tasks, except of run TC tests on different python's versions. пт, 22 янв. 2021 г. в 15:16, Igor Sapego : > Ivan, > > Though I generally agree with the approach you've suggested, I can see > a problem here. Since we now have a separate repos for thin clients, for > some features we may need to introduce changes to Ignite and python-thin > repos in a single ticket and we should have an ability to run tests on with > changes on both python client and server nodes. Current TC suites provide > such ability, Travis does not. So I believe, it's too soon to abandon TC > for thin > clients, at least until we could solve the issue I've described. > > Best Regards, > Igor > > > On Fri, Dec 25, 2020 at 1:49 PM Nikolay Izhikov > wrote: > > > Hello, Ivan. > > > > I’m +1 for your proposal. > > > > > 25 дек. 2020 г., в 13:14, Ivan Daschinsky > > написал(а): > > > > > > Hi folks! > > > > > > Since we already have a separate repo for thin-clients [1], [2] > > > I'd like to propose some improvements in development process/ > > > > > > 1. We should simplify and automate unit tests run for different > versions > > of > > > python > > > 2. We should add travis integration per commit and pr. Tests could be > run > > > against latest dockered image of ignite > > > 3. There should be ability to run tests against multiple pythons on TC > > > 4. For thin client development process, travis should be the first > > option. > > > TC suite should be used only to check that compatibility is not broken > > > and when new functionality is developed (rare case). > > > > > > I've prepared fix [3], you can see successful builds for travis. It > uses > > > tox [5], the most common tool to run tests in multiple environments. > > > There are few environments set up in tox.ini -- with and without > docker, > > > with or without ssl, etc. This helped a lot > > > to setup travis CI build (you can see in commits list of PR) and > simplify > > > run tests for developers. Also docker-compose was introduced > > > to help python thin client developers. > > > > > > But I need some assistance for TC: > > > 1. There is outdated python setuptools on TC agents, so tests cannot be > > run > > > with updated pytest etc. > > > 2. Multiple pythons should be installed on TC agents (via > > > https://github.com/pyenv/pyenv), latest minor versions > > > for 3.6, 3.7 and 3.8 > > > 3. After that, TC job should be changed to utilize tox > > > > > > WDYT about this initiative? > > > > > > > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-13767 > > > [2] -- https://github.com/apache/ignite-python-thin-client > > > [3] -- https://issues.apache.org/jira/browse/IGNITE-13903 > > > [4] -- > > https://github.com/apache/ignite-python-thin-client/pull/1/commits > > > [5] -- https://tox.readthedocs.io/en/latest/ > > > > > > -- > > > Sincerely yours, Ivan Daschinskiy > > > > > -- Sincerely yours, Ivan Daschinskiy
[jira] [Created] (IGNITE-14038) Separate JVM settings in the ducktests.
Vladimir Steshin created IGNITE-14038: - Summary: Separate JVM settings in the ducktests. Key: IGNITE-14038 URL: https://issues.apache.org/jira/browse/IGNITE-14038 Project: Ignite Issue Type: Sub-task Reporter: Vladimir Steshin Assignee: Vladimir Steshin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14037) Separate JVM settings in the ducktests.
Vladimir Steshin created IGNITE-14037: - Summary: Separate JVM settings in the ducktests. Key: IGNITE-14037 URL: https://issues.apache.org/jira/browse/IGNITE-14037 Project: Ignite Issue Type: Improvement Reporter: Vladimir Steshin Assignee: Vladimir Steshin -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] Python thin client development approach.
Ivan, Though I generally agree with the approach you've suggested, I can see a problem here. Since we now have a separate repos for thin clients, for some features we may need to introduce changes to Ignite and python-thin repos in a single ticket and we should have an ability to run tests on with changes on both python client and server nodes. Current TC suites provide such ability, Travis does not. So I believe, it's too soon to abandon TC for thin clients, at least until we could solve the issue I've described. Best Regards, Igor On Fri, Dec 25, 2020 at 1:49 PM Nikolay Izhikov wrote: > Hello, Ivan. > > I’m +1 for your proposal. > > > 25 дек. 2020 г., в 13:14, Ivan Daschinsky > написал(а): > > > > Hi folks! > > > > Since we already have a separate repo for thin-clients [1], [2] > > I'd like to propose some improvements in development process/ > > > > 1. We should simplify and automate unit tests run for different versions > of > > python > > 2. We should add travis integration per commit and pr. Tests could be run > > against latest dockered image of ignite > > 3. There should be ability to run tests against multiple pythons on TC > > 4. For thin client development process, travis should be the first > option. > > TC suite should be used only to check that compatibility is not broken > > and when new functionality is developed (rare case). > > > > I've prepared fix [3], you can see successful builds for travis. It uses > > tox [5], the most common tool to run tests in multiple environments. > > There are few environments set up in tox.ini -- with and without docker, > > with or without ssl, etc. This helped a lot > > to setup travis CI build (you can see in commits list of PR) and simplify > > run tests for developers. Also docker-compose was introduced > > to help python thin client developers. > > > > But I need some assistance for TC: > > 1. There is outdated python setuptools on TC agents, so tests cannot be > run > > with updated pytest etc. > > 2. Multiple pythons should be installed on TC agents (via > > https://github.com/pyenv/pyenv), latest minor versions > > for 3.6, 3.7 and 3.8 > > 3. After that, TC job should be changed to utilize tox > > > > WDYT about this initiative? > > > > > > [1] -- https://issues.apache.org/jira/browse/IGNITE-13767 > > [2] -- https://github.com/apache/ignite-python-thin-client > > [3] -- https://issues.apache.org/jira/browse/IGNITE-13903 > > [4] -- > https://github.com/apache/ignite-python-thin-client/pull/1/commits > > [5] -- https://tox.readthedocs.io/en/latest/ > > > > -- > > Sincerely yours, Ivan Daschinskiy > >
[jira] [Created] (IGNITE-14036) Tracing: add ability to trace compute operations.
Alexander Lapin created IGNITE-14036: Summary: Tracing: add ability to trace compute operations. Key: IGNITE-14036 URL: https://issues.apache.org/jira/browse/IGNITE-14036 Project: Ignite Issue Type: Bug Reporter: Alexander Lapin Assignee: Alexander Lapin After implementing update and check whether removeAll() and clear() traced properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14035) Table access public API
Andrey Mashenkov created IGNITE-14035: - Summary: Table access public API Key: IGNITE-14035 URL: https://issues.apache.org/jira/browse/IGNITE-14035 Project: Ignite Issue Type: Sub-task Reporter: Andrey Mashenkov Create table access API (incl. Record and KV concepts). Cover the next cases with Examples of how API can be used: * Simple Record case. * Simple KV case. * Truncated classes. * Custom serialization and BinaryObject concept. * Conditional serialization. * Inheritance mapping single table strategy (wide table schema vs conditional serialization) * Transition from "schemaless" (pure binary KV case) to a schema powered. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14034) Calcite integration. indexCondition refactoring
Konstantin Orlov created IGNITE-14034: - Summary: Calcite integration. indexCondition refactoring Key: IGNITE-14034 URL: https://issues.apache.org/jira/browse/IGNITE-14034 Project: Ignite Issue Type: Improvement Components: sql Reporter: Konstantin Orlov Currently IndexCondition is quite cumbersome and hard to understand. The difference between bounds and conditions is unclear as well as unclear what should be used to estimate a selectivity and what should be used to estimate a self cost. Thus I suggest to change it in a follow way: * remove [lower|upper]Cond * bounds remains as is * self cost estimation of an AbstractIndex should be calculated with regard to bounds * selectivity should be calculated with regards to whole condition that is member of ProjectableFilterableTableScan -- This message was sent by Atlassian Jira (v8.3.4#803005)
