Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4956
---
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/5072
Ignite 9941IGNITE-9941 Web Console: Add option to disable self-registration
You can merge this pull request into a Git repository by running:
$ git pull
Hey Scott,
Great to know, welcome to the community!
What exactly do you like to contribute back? Please start a separate
discussion with the most meaningful topic.
Also, if you can post a blog post about your architecture at VMWare will be
glad to mention it on the "Ignite in Production" page:
Hi Everyone,
I'm following the instructions from
https://ignite.apache.org/community/contribute.html. I'd like to contribute
some of the code I've been working on in order to continue evolving Ignite.
I've been evangelizing Ignite at VMware and am in the process of locking
down our next-gen
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/5071
Ignite 9976 mass run (fs test)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-9976-FULLSYNC
Alternatively you can review
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/5070
ignite-9650: Added DECIMAL type to jdbc metadata.
DECIMAL type earlier was treated as OTHER type by jdbc metadata.
Added mapping code for this type. Added regression tests.
You can
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/5069
Ignite 9841
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9841
Alternatively you can review and apply these
GitHub user macrergate opened a pull request:
https://github.com/apache/ignite/pull/5068
Ignite 2.5.1 p12 snap fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-2.5.1-p12-snap-fix
Alternatively
Dmitry Konstantinov created IGNITE-9993:
---
Summary: Values cached in WB store are locked during a batch flush
Key: IGNITE-9993
URL: https://issues.apache.org/jira/browse/IGNITE-9993
Project:
dspavlov opened a new pull request #43: IGNITE-9848 load all builds
URL: https://github.com/apache/ignite-teamcity-bot/pull/43
IGNITE-9848
[TC Bot] Background upload of all builds from TC to the bot DB
This is an automated
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/5067
IGNITE-9420 Proper recovery
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-9420-proper-recovery
Alternatively
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/5066
IGNITE-9454 Support CACHE_CREATE, CACHE_DESTROY, JOIN_AS_SERVER permiâ¦
â¦ssions in SecurityPermissionSetBuilder.
You can merge this pull request into a Git repository by running:
$ git pull
ARomantsov created IGNITE-9992:
--
Summary: Add some command to calculate hast sum per primary
partition in product
Key: IGNITE-9992
URL: https://issues.apache.org/jira/browse/IGNITE-9992
Project: Ignite
asfgit closed pull request #41: IGNITE-9940 [TC Bot] Sort pull requests by
update time
URL: https://github.com/apache/ignite-teamcity-bot/pull/41
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:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5048
---
asfgit closed pull request #42: IGNITE-9894 [TC Bot] Change of JIRA link name
URL: https://github.com/apache/ignite-teamcity-bot/pull/42
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
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/5065
Limit test execution time to 10 sec
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite 10sec-test-limit
Alternatively
Hi guys,
I need your advice here. As some of you probably know we have
Windows installers for ODBC in our binary releases, so users won't need
to build Ignite C++ if all they want is to install and use our ODBC driver.
However, as we build driver with MSVC 10 when we are preparing our
binary
asfgit closed pull request #35: Ignite 9848 load all builds
URL: https://github.com/apache/ignite-teamcity-bot/pull/35
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub
Stepan Pilschikov created IGNITE-9991:
-
Summary: thin clients: can't get cache by array key for PHP, JS
and Python clients
Key: IGNITE-9991
URL: https://issues.apache.org/jira/browse/IGNITE-9991
Hi Igor,
Yes, it sounds reasonable, agree.
P.
On Wed, Oct 24, 2018 at 7:42 AM Igor Sapego wrote:
> Pavel,
>
> Can we add a proper check and throw proper exception
> when trying to deserialize enum value? NPE does not say
> anything to a user.
>
> Best Regards,
> Igor
>
>
> On Wed, Oct 24,
Alexand Polyakov created IGNITE-9990:
Summary: Control.sh utility should request a password if necessary.
Key: IGNITE-9990
URL: https://issues.apache.org/jira/browse/IGNITE-9990
Project: Ignite
Pavel,
Can we add a proper check and throw proper exception
when trying to deserialize enum value? NPE does not say
anything to a user.
Best Regards,
Igor
On Wed, Oct 24, 2018 at 5:34 PM Pavel Petroshenko
wrote:
> Hi Stepan,
>
> Nodejs and PHP clients do not support enum type registration
Hi Stepan,
Nodejs and PHP clients do not support enum type registration (and hence no
tests). So enum type must be registered from somewhere else in order to be
put or get from the Thin clients.
If you register the type say from Java, then put/get for Enum values should
work from the Thin
Hi, all,
I was trying to fix IGNITE-7153 which relates to parsing incomplete REDIS
packet larger than 8192 bytes. However, I found a random problem which is
reproducible on TC as well.
That said, GridNioServerRead.processRead() :
- int cnt = sockCh.read(readBuf);
sometimes does not read the
ololo3000 opened a new pull request #42: IGNITE-9894 Change of JIRA link name
URL: https://github.com/apache/ignite-teamcity-bot/pull/42
This is an automated message from the Apache Git Service.
To respond to the message,
Hello.
Deisgn updated [1]
Please, share your feedback
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381
В Вт, 23/10/2018 в 21:49 +0300, Nikolay Izhikov пишет:
> Hello, Anton.
>
> Thank you for your very usefull feedback!
>
> I accept your proposals.
> Seems it
ololo3000 opened a new pull request #41: IGNITE-9940 Sort pull requests by
update time
URL: https://github.com/apache/ignite-teamcity-bot/pull/41
This is an automated message from the Apache Git Service.
To respond to the
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/5064
IGNITE-7072: IgniteCache.replace(k, v, nv) fix for binary mode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/5063
IGNITE-9753 Several optimization of validate_indexes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9753
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/5062
IGNITE-9917 Write proper tests for start/stop client.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9917
Pavel Kuznetsov created IGNITE-9989:
---
Summary: JDBC v2: getPrimaryKeys always returns constant
COLUMN_NAME, KEY_SEQ, PK_NAME
Key: IGNITE-9989
URL: https://issues.apache.org/jira/browse/IGNITE-9989
Hi Alex,
I wonder what problem you wish to solve. Pre-touching memory looks like a
solution.
But what is the problem? Am I getting it right that it is desired to avoid
OOM (of some kind)
in unpredictable moment of Ignite process execution? If so there could be
number of ways to tackle it.
I am
Val,
I'm working on this issue right now.
I don't see an ultimate problem here. The discovery data can be
deserialized using a system class loader.
Serialized representation is stored in
*CacheContinuousQueryDeployableObject.*
The actual deserialization happens later, when any class loader can be
Ivan Bessonov created IGNITE-9987:
-
Summary: Do not block reading during client node start/stop.
Key: IGNITE-9987
URL: https://issues.apache.org/jira/browse/IGNITE-9987
Project: Ignite
Issue
GitHub user pavel-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/5061
IGNITE-3467: Return "DATABASE" as catalog name.
Instead of returning "null" we now return "DATABASE" string constant.
Changes affect only jdbc v2 and thin driver (no changes in server
Ryabov Dmitrii created IGNITE-9986:
--
Summary:
TcpDiscoverySelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished is
flaky
Key: IGNITE-9986
URL: https://issues.apache.org/jira/browse/IGNITE-9986
asfgit closed pull request #36: IGNITE-9645 [TC Bot] Add comparison of failed
tests lists in two date intervals
URL: https://github.com/apache/ignite-teamcity-bot/pull/36
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/5060
IGNITE-9890 Refactor CachePartitionPartialCountersMap#fromCountersMapâ¦
â¦, no need to sort partitions any time it called.
You can merge this pull request into a Git repository by running:
Denis,
We run must of our production DBs systems without any swapping space,
because the 10-100x drop in throughput if such systems start paging makes
them worse than useless. However, we don't get OOM on them until all the
pages are dirty, since LINUX will page out read-only (code) pages or
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5023
---
Igniters,
thank you for your feedback.
I haven't seen any arguments against making abbreviation optional and not
mandatory.
So, could we update our wiki with code style to reflect our new vision on
abbreviations?
On Tue, Oct 23, 2018 at 2:01 PM Dmitriy Pavlov
wrote:
> Hi Ivan
>
> if by
Igor Seliverstov created IGNITE-9985:
Summary: MVCC TX: fix backup mappings
Key: IGNITE-9985
URL: https://issues.apache.org/jira/browse/IGNITE-9985
Project: Ignite
Issue Type: Task
Andrey Aleksandrov created IGNITE-9984:
--
Summary: Documentation for EVT_MANAGEMENT_TASK_STARTED will be
required.
Key: IGNITE-9984
URL: https://issues.apache.org/jira/browse/IGNITE-9984
Project:
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/5059
IGNITE-9983: add ignite inspections config for teamcity
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-9983
Maxim Muzafarov created IGNITE-9983:
---
Summary: Add an inspection configuration for TC suite with enabled
short list of rules
Key: IGNITE-9983
URL: https://issues.apache.org/jira/browse/IGNITE-9983
asfgit closed pull request #39: IGNITE-9901 Persistent queue for visas added
URL: https://github.com/apache/ignite-teamcity-bot/pull/39
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
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5006
---
Hello, Valentin.
> What I don't agree with is that replacing thick client with thin client is a
> way to fix usability issues.
I think it will fix some of them.
> will potentially compromise the performance
As I mentioned earlier, I want to provide easy way to play with integration.
For
Stepan Pilschikov created IGNITE-9982:
-
Summary: SQLLine: can't run with option --autoCommit=false or true
Key: IGNITE-9982
URL: https://issues.apache.org/jira/browse/IGNITE-9982
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5011
---
Hello, Igniters.
We have 3 ticket mapped to 2.7 today:
Igor Seliverstov - IGNITE-9892 - MVCC: Exchange hangs on mvcc coordinator fail
Roman Kondakov - IGNITE-9828 - MVCC: Continuous query failover.
Roman Kondakov - IGNITE-9928 - MVCC TX: Bug in SQL query mapping.
В Вт, 23/10/2018 в 15:01
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5030
---
Alex,
I think offheap memory preallocation will not be helpful as you expect:
1. We still will not have any guarantee JVM process won't be killed by
OOM-killer due to memory overcommiting e.g. for GC needs.
as JVM allocates memory for internal needs in same process memory space.
2. Startup
Docs [1] says, that OOM can also be thrown when native library can't
allocate memory chunk if physical memory (ram + swap).
>> Shouldn't OOM happen if you're trying to allocate beyond the virtual
memory capacity (beyond X GB)?
With 64-bit addressing you have some exabytes of virtual memory, is it
Github user dmekhanikov closed the pull request at:
https://github.com/apache/ignite/pull/4530
---
56 matches
Mail list logo
