Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/3190
---
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/5629
IGNITE-10624 Update deployment id for recovered cache after join to topology
You can merge this pull request into a Git repository by running:
$ git pull
The main concern is related to chances that newcomer will have to obtain a
review support from the community.
Actually, a lot of people doing their best to provide a feedback to
newcomers, and count of issues still in PA state goes down (84 is a
relatively small count of issues in PA state). But
Vovan,
1) Tomorrow in core-module.
2) I believe that nothing, old JUnit3 would work if they are a new one.
Otherwise, they need to fix merge conflict and add @Test on their new test.
And I think that it's unavoidable, we couldn't ask all people to finish
their current activity and not start a new
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/4547
---
Pavel Kovalenko created IGNITE-10625:
Summary: Do first checkpoint on node start before join to topology
Key: IGNITE-10625
URL: https://issues.apache.org/jira/browse/IGNITE-10625
Project: Ignite
Vladimir, AFAIK there will be no single change for overall migration. All
migration will be in a step-by-step manner and mostly transparent for
contributors.
Both approaches 3&4 will be available for some time.
First of all, we need an opportunity to run existing integration tests in
JUnit4.
Vladimir.
Since we are talking about internal component(Spark Data Frame integration)
can we use same technique as JdbcRequestHandler to obtain columns metadata?
Seems, code above will fetch up to date columns info:
Got it. Thank you.
пн, 10 дек. 2018 г. в 20:52, Dmitriy Pavlov :
> Vladimir, AFAIK there will be no single change for overall migration. All
> migration will be in a step-by-step manner and mostly transparent for
> contributors.
>
> Both approaches 3&4 will be available for some time.
>
> First
zzzadruga opened a new pull request #97: IGNITE-10628 Add support for nightly
RunAll
URL: https://github.com/apache/ignite-teamcity-bot/pull/97
This is an automated message from the Apache Git Service.
To respond to the
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3964
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3906
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3980
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/4007
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3963
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3866
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3875
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3922
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3930
---
Forwarding to the dev list.
*Prachi*, could you please help us with 3-5? It requires minor updates on
the webpage.
*Sergey K.*, *Peter*, could you assist with 1 and 2?
--
Denis
On Fri, Dec 7, 2018 at 11:19 PM Nikolay Izhikov wrote:
> Hello, Igniters.
>
> Seems that our download page doesn't
Evgenii Zhuravlev created IGNITE-10627:
--
Summary: Support custom preferences like date format and other
similar features
Key: IGNITE-10627
URL: https://issues.apache.org/jira/browse/IGNITE-10627
Hi Vovan,
I just created JIRA ticket to address your concerns:
- https://issues.apache.org/jira/browse/IGNITE-10629
In brief, the plan is that a week or two after migration is over we will run
code inspection that detects JUnit 3 style tests that lack @Test annotation
and fix these tests if
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/2986
---
Hello, Dmitriy.
What, exactly concerns newcomers?
What is wrong with opened PR?
How project will benefit from closed PR?
> The same proposal is related to IEP statuses. If you were involved in an
IEP, please validate its status
+1. We should maintain IEP description up to date.
пн, 10 дек.
Github user dspavlov closed the pull request at:
https://github.com/apache/ignite/pull/1892
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3664
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3855
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3413
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3433
---
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/1955
---
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/2482
---
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/2121
---
Github user dspavlov closed the pull request at:
https://github.com/apache/ignite/pull/2276
---
Evgenii Zhuravlev created IGNITE-10626:
--
Summary: Save authenticated Webconsole session for more than one
page refresh
Key: IGNITE-10626
URL: https://issues.apache.org/jira/browse/IGNITE-10626
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/5541
---
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/5092
---
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/5219
---
Hello,
I would like add few minor clarifications to what Ed wrote.
1. After transition to JUnit4 is fully over (ETA this week) there won't be a
need to use @RunWith(JUnit4.class) anymore, so you will be writing test
classes as a normal JUnit 4 user, without any special scaffolding.
1.1. Please
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/4229
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3981
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/4895
---
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/4055
---
Pavel Kovalenko created IGNITE-10624:
Summary: Cache deployment id may be different that cluster-wide
after recovery
Key: IGNITE-10624
URL: https://issues.apache.org/jira/browse/IGNITE-10624
Ed,
Several questions from my side:
1) When the change is expected to be merged?
2) What contributors with opened PRs and new or updated JUnit3 tests are
supposed to do? Rewrite to JUnit4?
If yes, then we should give them time to have a chance to get used to new
approach and resolve possible
Github user nizhikov closed the pull request at:
https://github.com/apache/ignite/pull/5584
---
Nikolai Kulagin created IGNITE-10628:
Summary: Add support for nightly RunAll
Key: IGNITE-10628
URL: https://issues.apache.org/jira/browse/IGNITE-10628
Project: Ignite
Issue Type:
Oleg Ignatenko created IGNITE-10629:
---
Summary: Migration follow up: check for old style tests that could
be slipped through in transition period
Key: IGNITE-10629
URL:
NodeJs client:
--
Instruction -
https://github.com/nobitlost/ignite/blob/ignite--docs/modules/platforms/nodejs/README.md#publish-ignite-nodejs-client-on-npmjscom-instruction
Uploaded - https://www.npmjs.com/package/apache-ignite-client
PHP client:
---
Instruction -
Sergey Kozlov created IGNITE-10630:
--
Summary: Missed descriptions for ML packages
Key: IGNITE-10630
URL: https://issues.apache.org/jira/browse/IGNITE-10630
Project: Ignite
Issue Type: Bug
dspavlov opened a new pull request #98: IGNITE-10620: Tracked branches & Issue
detector unit tests
URL: https://github.com/apache/ignite-teamcity-bot/pull/98
This is an automated message from the Apache Git Service.
To
Sergey Kozlov created IGNITE-10631:
--
Summary: examples/sql/world.sql doesn't work for IgniteJdbcDriver
Key: IGNITE-10631
URL: https://issues.apache.org/jira/browse/IGNITE-10631
Project: Ignite
Agree with Dmitriy.
We use GitHub PRs in our workflow, therefore we should keep them in order.
We can close PRs that refer to closed tickets, this can be done with a
simple script.
On Tue, Dec 11, 2018 at 9:15 AM Павлухин Иван wrote:
> Nikolay,
>
> I must say that when I first saw 1K+ open
Pavel Tupitsyn created IGNITE-10634:
---
Summary: .NET: EntityFramework Core Second Level Cache
Key: IGNITE-10634
URL: https://issues.apache.org/jira/browse/IGNITE-10634
Project: Ignite
Issue
Nikolay,
I must say that when I first saw 1K+ open PRs my first thought was
that something was wrong with a review process. In my mind in not very
big project open PR list can reflect very well the real work in
progress. For bigger projects things become more complicated.
Dmitriy,
Do you have
Nikolay, Petr,
I have already registered the package `pyignite` on PyPI[1]. The person
who is going to take the responsibility of maintaining it should create
an account on PyPI and mail me in private, so that I can grant them the
necessary rights. They also must install twine[3].
The
Andrey created IGNITE-10635:
---
Summary: Ignite throws org.apache.ignite.IgniteCheckedException
Key: IGNITE-10635
URL: https://issues.apache.org/jira/browse/IGNITE-10635
Project: Ignite
Issue Type:
Vasiliy Sisko created IGNITE-10632:
--
Summary: Web console: Failed to show cache mode on query notebook
page.
Key: IGNITE-10632
URL: https://issues.apache.org/jira/browse/IGNITE-10632
Project: Ignite
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
Oleg Ignatenko created IGNITE-10633:
---
Summary: CacheEntryProcessorExternalizableFailedTest fails on
Teamcity when executed under JUnit 4
Key: IGNITE-10633
URL: https://issues.apache.org/jira/browse/IGNITE-10633
Hi Ivan,
Unfortunately, I don't have the necessary rights to close PRs. Only PR
author can close.
I can only imagine the following way: Produce fake commit(s) with message
Fixes #. But this may be acceptable if PR author is not responding.
Simple expiration policy may have its own issues.
Hi Igniters,
Infra changed notifications, so now GitHub emails are being sent to
notifications@
Web UI: https://lists.apache.org/list.html?notificati...@ignite.apache.org
You may subscribe to the list notifications-subscr...@ignite.apache.org
Sincerely,
Dmitriy Pavlov
ср, 5 дек. 2018 г. в
Hello, Ivan.
Personally, I keep my PR's clear.
So, I don't have dozens of opened PR.
But, I don't support Dmitriy proposal for several reasons:
1. We introduce some new, not required, level of bureaucracy.
From my experience - not required bureaucracy is a BAD thing.
2. We spread our work
My point is - close your outdated PRs/if you don't need. It is not a
pattern nor enforcement nor bureaucracy.
You're absolutely free to use PRs in any way you like to (e.g. experiments
with TC runs).
Now count of PRs shocks newcomers.
вт, 11 дек. 2018 г. в 10:10, Nikolay Izhikov :
> Hello,
Hi Oleg,
Yes, makes perfect sense. Thank you.
On Mon, Dec 10, 2018 at 10:14 PM oignatenko wrote:
> Hi Vovan,
>
> I just created JIRA ticket to address your concerns:
> - https://issues.apache.org/jira/browse/IGNITE-10629
>
> In brief, the plan is that a week or two after migration is over we
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/5617
IGNITE-10189 Added support for SSL Ciphers for control.sh
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Github user akuznetsov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/5392
---
Vyacheslav Daradur created IGNITE-10615:
---
Summary: Ignite Compatibility: fix arguments' checking in the node
runner
Key: IGNITE-10615
URL: https://issues.apache.org/jira/browse/IGNITE-10615
Alexey,
Have a look at the 'PluginProvider' interface, if you implemented a
telemetry service as a plugin:
* plugin may be placed in the 'web-console' module;
* plugin is initialized at node startup and is stopped at node shutdown;
* plugin have access to all Ignite's internals through context;
*
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5429
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5539
---
Pavel Konstantinov created IGNITE-10616:
---
Summary: Web console: new security token must be applied
immediately
Key: IGNITE-10616
URL: https://issues.apache.org/jira/browse/IGNITE-10616
SomeFire opened a new pull request #96: fix typo in schedulers
URL: https://github.com/apache/ignite-teamcity-bot/pull/96
This is an automated message from the Apache Git Service.
To respond to the message, please log on
>From my point of view, it's important to further develop the thin client.
Users should be able to use most of Ignite's components via thin
client, as far as possible, just for example:
* transactional CRUD operations over data in the cluster;
* deploy/undeploy and monitor services in the Service
Vasiliy Sisko created IGNITE-10617:
--
Summary: Web console: Invalid class name in
frontend/app/components/connected-clusters-dialog/components/list/controller.js
Key: IGNITE-10617
URL:
Maxim Muzafarov created IGNITE-10619:
Summary: Add support for ReadableByteChannel, WritableByteChannel
over CommunicationSpi
Key: IGNITE-10619
URL: https://issues.apache.org/jira/browse/IGNITE-10619
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/5619
IGNITE-10619: CommunicationSpi support channels initial commit
- GridNioServer supports channel creation from GridNioSession
- rework createTcpClient method
- new GridIoManager channel
Dmitriy,
You confirmed that fix should be reverted and reworked last Friday.
Why it still not reverted?
On Mon, Dec 10, 2018 at 12:46 AM Dmitrii Ryabov
wrote:
> Agree, it is reasonable to revert.
> пт, 7 дек. 2018 г. в 18:44, Dmitriy Pavlov :
> >
> > Hi Ilya,
> >
> > thank you for noticing.
>
Prachi,
Can you help to export all the latest version of all documents to me?
I am ready to make a synchronization of the chinese version of the document.
thanks!
在 2018/6/2 上午4:38, Prachi Garg 写道:
Please see attached.
On Fri, Jun 1, 2018 at 9:22 AM, 李玉珏@163 <18624049...@163.com
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5585
---
Dmitriy Pavlov created IGNITE-10620:
---
Summary: [TC Bot] Implement Tracked Branches processor and
IssueDetector unit tests
Key: IGNITE-10620
URL: https://issues.apache.org/jira/browse/IGNITE-10620
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5409
---
asfgit closed pull request #96: fix typo in schedulers
URL: https://github.com/apache/ignite-teamcity-bot/pull/96
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request
asfgit closed pull request #94: Visa History page fix
URL: https://github.com/apache/ignite-teamcity-bot/pull/94
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request
Yury Gerzhedovich created IGNITE-10621:
--
Summary: Track all running queries
Key: IGNITE-10621
URL: https://issues.apache.org/jira/browse/IGNITE-10621
Project: Ignite
Issue Type: Task
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4685
---
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/5572
---
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/5593
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5590
---
GitHub user ygerzhedovich opened a pull request:
https://github.com/apache/ignite/pull/5620
IGNITE-10621
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10621
Alternatively you can review and apply
Anton, I was expecting that you revert, because you wanted to do it.
Provided that I agree that fix could be reverted because of both functional
and style possible improvements, does not mean I believe it is the only
option and it should be reverted.
Even if I agree to revert doesn't mean all
Anton Kalashnikov created IGNITE-10622:
--
Summary: Undelivered ensure message to some nodes
Key: IGNITE-10622
URL: https://issues.apache.org/jira/browse/IGNITE-10622
Project: Ignite
Github user voropava closed the pull request at:
https://github.com/apache/ignite/pull/5563
---
Github user voropava closed the pull request at:
https://github.com/apache/ignite/pull/5425
---
GitHub user voropava opened a pull request:
https://github.com/apache/ignite/pull/5621
Ignite 2.5.1 p162
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p162
Alternatively you can review and
Reverted.
https://issues.apache.org/jira/browse/IGNITE-8227 reopened
пн, 10 дек. 2018 г. в 16:23, Dmitriy Pavlov :
> Anton, I was expecting that you revert, because you wanted to do it.
>
> Provided that I agree that fix could be reverted because of both
> functional and style possible
Eduard Shangareev created IGNITE-10623:
--
Summary: Possible JVM crash in case of stopping node with errors
Key: IGNITE-10623
URL: https://issues.apache.org/jira/browse/IGNITE-10623
Project: Ignite
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5622
IGNITE-10472: MVCC: Add Dependency Injection support for EntryProcessor.
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/5623
IGNITE-10623 Possible JVM crash when node stopped with errors
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/5624
IGNITE-10556 Skip records deserialization on recovery
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10556
GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/5625
IGNITE-8717 Cache configuration was moved to metastore
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
1 - 100 of 116 matches
Mail list logo
