Pavel Tupitsyn created IGNITE-13883:
---
Summary: .NET: Performance: Refactor
BinarySystemHandlers.TryReadSystemType to switch-case
Key: IGNITE-13883
URL: https://issues.apache.org/jira/browse/IGNITE-13883
Hi,
Is it right that suggested Alpha will not be able to perform any
operations with data (tables, caches)? In that case Alpha naming
confuses me. Actually do not know how such kind of demo releases
should be attributed.
2020-12-21 20:42 GMT+03:00, Denis Magda :
> Certainly, the end of Jan is mor
pavlukhin merged pull request #10:
URL: https://github.com/apache/ignite-3/pull/10
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to t
Ticket was merged. Thanks to all participants.
2020-12-21 10:12 GMT+03:00, Ivan Pavlukhin :
> Folks,
>
> I will merge the PR tomorrow if there is no objections.
>
> 2020-12-19 0:56 GMT+03:00, Valentin Kulichenko
> :
>> Folks,
>>
>> Can someone take a look at this PR? I'm generally OK with the chan
I noticed some free-from commit messages in ignite-3 repository. I
think we should use ticket-based workflow and commit messages as
usual.
[1] https://github.com/apache/ignite-3/commits/main
2020-12-21 10:55 GMT+03:00, Petr Ivanov :
> There is no problem to have both in new repository, if skilled
Also I noticed that ignite-3 repository has "main" but not "master"
branch. Who can shed light on this? Did not find an explanation in
this thread.
2020-12-22 13:09 GMT+03:00, Ivan Pavlukhin :
> I noticed some free-from commit messages in ignite-3 repository. I
> think we should use ticket-based w
Ivan, it is the new GitHub default
"On Oct. 1, 2020, any new repositories you create will use main as the
default branch, instead of master" [1]
[1]
https://www.zdnet.com/article/github-to-replace-master-with-main-starting-next-month/
On Tue, Dec 22, 2020 at 1:12 PM Ivan Pavlukhin wrote:
> Als
Pavel, thanks for explanation!
2020-12-22 13:34 GMT+03:00, Pavel Tupitsyn :
> Ivan, it is the new GitHub default
>
> "On Oct. 1, 2020, any new repositories you create will use main as the
> default branch, instead of master" [1]
>
> [1]
> https://www.zdnet.com/article/github-to-replace-master-with
Hi Igniters!
New wallpapers are already in our special repository [1]. Some of them you
can also use as zoom background during the calls.
GridGain DevRel team wishes you happy holidays!
[1]
https://github.com/apache/ignite-website/tree/master/images/wallpapers/2021
--
Cheers,
Kseniya
Devrel a
Hello everyone,
In my opinion, it is indeed better to limit storing to the metastore by
primitive type(map or list are also possible) or use the POJO from the ignite
core.
As Kirill correctly notice, right now, it is a problem not inside of the
distributed metastore but inside of discovery.
In
Yaroslav Molochkov created IGNITE-13884:
---
Summary: Merge docs into 2.9.1
Key: IGNITE-13884
URL: https://issues.apache.org/jira/browse/IGNITE-13884
Project: Ignite
Issue Type: Bug
Hello, Anton.
> or use the POJO from the ignite core.
How it differs from the current implementation?
> As I can see you have tests only for one node but what happens if different
> nodes have different filters?
The error will happen.
Please, don’t forget that we are talking about two scenar
Alexey Scherbakov created IGNITE-13885:
--
Summary: Investigate jraft implementation for Ignite3 replication
module based on RAFT protocol.
Key: IGNITE-13885
URL: https://issues.apache.org/jira/browse/IGNITE-13
Denis Mekhanikov created IGNITE-13886:
-
Summary: Change units of cache-related histograms to milliseconds
Key: IGNITE-13886
URL: https://issues.apache.org/jira/browse/IGNITE-13886
Project: Ignite
kgusakov opened a new pull request #11:
URL: https://github.com/apache/ignite-3/pull/11
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
> How it differs from the current implementation?
There are no differences in implementation. But according to the original
topic, plugins or other external things can write to metastore their own
classes. I just said that according to current architecture it is not a good
idea to do that becaus
Hello, Anton.
Thanks for the answer!
> Only maybe, it makes sense to remove such records (with all history) instead
> of filtering them.
I don’t think we should do this, by default.
Imagine scenario #1:
1. Update the plugin to the next bugged version. Some class that is written to
the metas
Maxim Muzafarov created IGNITE-13887:
Summary: Checkpoint write lock missed during snapshot operation
Key: IGNITE-13887
URL: https://issues.apache.org/jira/browse/IGNITE-13887
Project: Ignite
Ivan,
Yes, you are correct - no tables, caches, compute or any other major
features will be available.
Alpha releases are generally produced in the middle of the development
process for internal testing. In my view, that's exactly what the upcoming
release is, but let me know if you have a better
Amelchev Nikita created IGNITE-13888:
Summary: Provide the utility to output performance statistics
operations to the console
Key: IGNITE-13888
URL: https://issues.apache.org/jira/browse/IGNITE-13888
Amelchev Nikita created IGNITE-13889:
Summary: Remove web-resources from the source of the performance
report
Key: IGNITE-13889
URL: https://issues.apache.org/jira/browse/IGNITE-13889
Project: Ign
Amelchev Nikita created IGNITE-13891:
Summary: Provide the ability to configure performance report
Key: IGNITE-13891
URL: https://issues.apache.org/jira/browse/IGNITE-13891
Project: Ignite
Amelchev Nikita created IGNITE-13890:
Summary: Remove zip-file with web-resources from the jar
Key: IGNITE-13890
URL: https://issues.apache.org/jira/browse/IGNITE-13890
Project: Ignite
Is
Amelchev Nikita created IGNITE-13892:
Summary: Improve log message of start/stop performance statistics
collection
Key: IGNITE-13892
URL: https://issues.apache.org/jira/browse/IGNITE-13892
Project
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New test failure in master-nightly
GracefulShutdownTest.testThatExcludedNodeListWithinMetastoreCleanedUpAfterUpdatingFullMap
https://ci.ignite.apache.org/project.html?projectId=Igni
Amelchev Nikita created IGNITE-13893:
Summary: Optimize memory usage on export performance statistics to
JSON
Key: IGNITE-13893
URL: https://issues.apache.org/jira/browse/IGNITE-13893
Project: Ign
Hi Peter,
Thanks for reminding the nuances. It's been a while since I contributed to
the codebase.
Ok, then I think nobody will object that the docs will always be published
from a release branch such as ignite-2.9.1 and then we can commit to the
branch directly if 2.9.1 needs to be updated. Wrot
Valentin Kulichenko created IGNITE-13894:
Summary: Improve look&feel of the CLI tool
Key: IGNITE-13894
URL: https://issues.apache.org/jira/browse/IGNITE-13894
Project: Ignite
Issue Ty
vkulichenko opened a new pull request #12:
URL: https://github.com/apache/ignite-3/pull/12
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
29 matches
Mail list logo
