Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3271
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3232
---
Hi, Denis, how will the complexity of tasks be estimated?
On Fri, Dec 22, 2017 at 3:16 AM, Denis Magda wrote:
> Igniters,
>
> We at Ignite PMC put together a page with rules-of-thumb on when it’s a right
> time to promote a contributor to a committer:
> https://cwiki.apache.org/confluence/displ
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3273
IGNITE-6735
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6735-1
Alternatively you can review and apply thes
Vica Abramova created IGNITE-7286:
-
Summary: Web Console: We can't copy from the tables (in old design)
Key: IGNITE-7286
URL: https://issues.apache.org/jira/browse/IGNITE-7286
Project: Ignite
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/2748
---
Igniters,
I'm glad to announce that it is now possible to do Ignite.NET development
(build from sources, run tests) on Linux and macOS!
Changes are in master, see modules/platforms/dotnet/DEVNOTES.txt for
details.
Let me know if you have any questions.
Thanks,
Pavel
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/3273
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3005
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3269
---
Github user ybabak closed the pull request at:
https://github.com/apache/ignite/pull/2632
---
Pavel Tupitsyn created IGNITE-7287:
--
Summary: Thin client: idle connection timeout
Key: IGNITE-7287
URL: https://issues.apache.org/jira/browse/IGNITE-7287
Project: Ignite
Issue Type: Improve
Great news, Pavel! As a Linux user I will definitely try that and let you
know on results.
--Yakov
Hi, Pavel, thanks for this improvement, but as far as I understood it
is compatibility mode with .NET Сore.
Are you going to port Ignite to native .NET Core, maybe in the next
major release?
On Fri, Dec 22, 2017 at 1:55 PM, Yakov Zhdanov wrote:
> Great news, Pavel! As a Linux user I will definit
Hi Vyacheslav,
No, porting to .NET Core (actually, libraries should target .NET Standard
instead of .NET Core)
is not planned, since we maintain compatibility with .NET 4 and Visual
Studio 2010.
There is no reason to do the full port, since release binaries already work
on all platforms
(.NET 4+
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/3274
Ignite 1.8.17
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.17
Alternatively you can review and appl
Pavel Tupitsyn created IGNITE-7288:
--
Summary: Thin client: Allow partial cache configuration
Key: IGNITE-7288
URL: https://issues.apache.org/jira/browse/IGNITE-7288
Project: Ignite
Issue Typ
Ticket created: https://issues.apache.org/jira/browse/IGNITE-7288
I'll implement this next week.
On Fri, Dec 22, 2017 at 10:06 AM, Pavel Tupitsyn
wrote:
> Hi Denis,
>
> I think we can assign an id to each parameter. It is not difficult to add.
>
> > not to tell about this operation
> Hiding stuf
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3187
---
Hello!
I have reviewed your code and commented IGNITE-7107 for a list of potential
problem.
I think everything from the first "blocker" section ought to be fixed
before this patch is merged, while "nice to have" things may be spinned out
as separate tickets. I suggest moving scripts that don't wo
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/3275
Ignite 2.3 master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.3-master
Alternatively you can review and
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/3276
---
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/3276
Ignite 2.3.2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.3.2
Alternatively you can review and apply the
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/3277
ignite-6952 fix DirectByteBufferStreamImplV2#readArrayLE()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-69
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/3278
Ignite 2.1.10
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.10
Alternatively you can review and apply the
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3246
---
Ilya Kasnacheev wrote
> I have noticed that both spec and DEVNOTES are made to use tabs alongside
> with spaces. I thought we are avoiding tabs? Please confirm that usage of
> tabs is desired in this case.
My fault - got used to editing such files in default vim. Fixed and updated
vim settings to
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/3279
ignite-2.4.2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.2
Alternatively you can review and apply the
Evgenii Zhuravlev created IGNITE-7289:
-
Summary: ODBC: add possibility to reconnect to the cluster after
node failing
Key: IGNITE-7289
URL: https://issues.apache.org/jira/browse/IGNITE-7289
Projec
Alexey Goncharuk created IGNITE-7290:
Summary: Log when partition is moved to a LOST state
Key: IGNITE-7290
URL: https://issues.apache.org/jira/browse/IGNITE-7290
Project: Ignite
Issue Ty
Denis Magda created IGNITE-7291:
---
Summary: Apache Ignite "in use at" section
Key: IGNITE-7291
URL: https://issues.apache.org/jira/browse/IGNITE-7291
Project: Ignite
Issue Type: Bug
Hi Vyacheslav,
Some common sense, I presume. A committer who will be proposing a candidate can
use JIRA to see a total number of resolved tickets and Git history to get
insights on a complexity of every contribution.
Do you have any suggestions on this?
—
Denis
> On Dec 22, 2017, at 12:56 AM,
Pavel, thanks for a quick turnaround. Please ping Prachi when you merge the
improvement so that she can update the readme doc.
—
Denis
> On Dec 22, 2017, at 4:43 AM, Pavel Tupitsyn wrote:
>
> Ticket created: https://issues.apache.org/jira/browse/IGNITE-7288
> I'll implement this next week.
>
Denis Magda created IGNITE-7292:
---
Summary: Optimize Ignite main page load performance
Key: IGNITE-7292
URL: https://issues.apache.org/jira/browse/IGNITE-7292
Project: Ignite
Issue Type: Task
34 matches
Mail list logo
