Hello, Igniters.
We have *9* tickets mapped to 2.7 today
Vladimir, do you think 1 week delay will be enough to resolve all this tickets?
IGNITE-9828 Roman Kondakov MVCC: Continuous query failover.
IGNITE-9928 Igor SeliverstovMVCC TX: Late affinity assignment
support.
IG
Hello, Maxim.
Great job! Thank you!
Igniters, let's add this suite to the Run All!
It can help us improve code quality and check code style without human eyes.
В Пт, 26/10/2018 в 00:47 +0300, Maxim Muzafarov пишет:
> Igniters,
>
> The new `Inspections: Core` suite [2] configured on TeamCity (p
I have not checked the exact routine, but you need to reexecute read until it
returns -1 or if known that all bytes that are expected have been read (if
sockCh is based on some kind of input stream)
> Am 26.10.2018 um 04:24 schrieb Michael Fong :
>
> Bump!
>
> Anyone who could help me solve th
Bump!
Anyone who could help me solve this random issue? Thanks!
Regards,
Michael
On Wed, Oct 24, 2018 at 10:32 PM Michael Fong wrote:
> 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
Igniters,
The new `Inspections: Core` suite [2] configured on TeamCity (pass
successfully with - Inspections total: 0, errors: 0 ).
The next rules are enabled for this suite:
- `Missorted modifiers`;
- `'size() == 0' replaceable with 'isEmpty()'`;
- `Add missing @Override annotation`;
- `Fix u
Sergey Kozlov created IGNITE-10013:
--
Summary: Node restart may lead to NPE in
GridDhtPartitionsExchangeFuture
Key: IGNITE-10013
URL: https://issues.apache.org/jira/browse/IGNITE-10013
Project: Ignite
Prachi Garg created IGNITE-10012:
Summary: Add Transactional SQL feature description to Ignite
website
Key: IGNITE-10012
URL: https://issues.apache.org/jira/browse/IGNITE-10012
Project: Ignite
Dmitry,
Thanks for the pointers!
Would you be interested in sorting this out for the community by talking to
our ASF-mates who should know?
--
Denis
On Thu, Oct 25, 2018 at 3:21 AM Dmitriy Pavlov
wrote:
> Hi Igor,
>
> I'm not sure if someone in the community can know an answer to this
> quest
In my understanding, that's an easy operation to support - we just need to
allocate requested space and pre-touch it (iterate and fill out with 0).
Yes, it will increase the launch time but it's a valid use case. Some
companies do memory pre-touching on purpose.
--
Denis
On Thu, Oct 25, 2018 at
Hi Scott,
Thanks, the contributions looks valuable to me. As I see a community member
is already working with you. Hope the code will be merged soon!
--
Denis
On Thu, Oct 25, 2018 at 10:59 AM Scott Feldstein wrote:
> Hi Denis,
> Thanks!
>
> This is what I'm trying to contribute
> jira: https
Nikita,
I like your suggestion. It looks more expressive for me than existing
throwing version.
чт, 25 окт. 2018 г. в 21:07, Nikita Amelchev :
> Hi, Igniters.
>
> I suggest improving new listening test logger.
>
> I found usage case when needs wait for conditions for test duration
> optimization
Hi, Igniters.
I suggest improving new listening test logger.
I found usage case when needs wait for conditions for test duration
optimization.
For example, that messages A and B will be logged.
For now, LogListener.check() doesn't return checking result as boolean.
It throws the exception if con
Hi Denis,
Thanks!
This is what I'm trying to contribute
jira: https://issues.apache.org/jira/browse/IGNITE-9893
pullRequest: https://github.com/apache/ignite/pull/5008
WRT the blog, we actually discussed this at the in-memory conference. At
the beginning of the year we'll start to make our u
Ilya Kasnacheev created IGNITE-10011:
Summary: Pages leak suspicion in PDS
Key: IGNITE-10011
URL: https://issues.apache.org/jira/browse/IGNITE-10011
Project: Ignite
Issue Type: Bug
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/5084
IGNITE-10003 Changed checkpointReadLock timeout failure type.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrey-kuznetsov/ignite
Hi Pavel,
1) I fixed the broken link. Thanks for pointing out.
2) Yes, that is a common problem, and as far as I know, we don't have
such a check, but we will when we adopt the new docs publishing process
(markdown-to-html-pulled-from-github-based process).
Cheers,
Artem
On 25.10.2018 16:36
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/5083
9986 flakiness
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SomeFire/ignite 9986-flakiness
Alternatively you can review and apply these ch
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/5082
IGNITE-9986
TcpDiscoverySelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished is
flaky
You can merge this pull request into a Git repository by running:
$ git pull https://github.co
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/5081
IGNITE-9997
Fix IgniteDiagnosticMessagesTest.testLongRunningTx test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite ignite
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/5080
IGNITE-10009: ODBC fix for escaped table names
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10009
Alternative
Sergey Kozlov created IGNITE-10010:
--
Summary: Node halted if table was dropped
Key: IGNITE-10010
URL: https://issues.apache.org/jira/browse/IGNITE-10010
Project: Ignite
Issue Type: Bug
Igor Sapego created IGNITE-10009:
Summary: ODBC: SQLColumns does not work for tables with escape
sequences in name
Key: IGNITE-10009
URL: https://issues.apache.org/jira/browse/IGNITE-10009
Project: Ig
Alexey Platonov created IGNITE-10008:
Summary: Need to investigate why these tests is failed after
consistentID set
Key: IGNITE-10008
URL: https://issues.apache.org/jira/browse/IGNITE-10008
Projec
Sergey Kozlov created IGNITE-10007:
--
Summary: Deactivation hangs if an open transaction exists
Key: IGNITE-10007
URL: https://issues.apache.org/jira/browse/IGNITE-10007
Project: Ignite
Issue
Hi, Ivan
Let me try to explain. I think that there are 2 goals that are mostly
applicable for prod systems:
1. I can agree with Dave that swap is not a good case for performance and
disk resource. It is possible that other applications can consume memory
that is free after Ignite was started. In th
Sergey created IGNITE-10006:
---
Summary: Checking for each operation within a transaction to
calculate how long it took
Key: IGNITE-10006
URL: https://issues.apache.org/jira/browse/IGNITE-10006
Project: Ignit
Pavel Kuznetsov created IGNITE-10005:
Summary: SQL table catalog documentation
Key: IGNITE-10005
URL: https://issues.apache.org/jira/browse/IGNITE-10005
Project: Ignite
Issue Type: Task
Sergey Kozlov created IGNITE-10004:
--
Summary: Parse error leads to leave the transaction
Key: IGNITE-10004
URL: https://issues.apache.org/jira/browse/IGNITE-10004
Project: Ignite
Issue Type:
Andrey Kuznetsov created IGNITE-10003:
-
Summary: Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR
when checkpoint read lock timeout detected
Key: IGNITE-10003
URL: https://issues.apache.org/jira/browse/IG
Andrew Mashenkov created IGNITE-10002:
-
Summary: MVCC: Create "Cache 2" test suite for MVCC mode.
Key: IGNITE-10002
URL: https://issues.apache.org/jira/browse/IGNITE-10002
Project: Ignite
Andrew Mashenkov created IGNITE-10001:
-
Summary: MVCC: Make existed tests run in MVCC mode as well.
Key: IGNITE-10001
URL: https://issues.apache.org/jira/browse/IGNITE-10001
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4985
---
Vladimir Ozerov created IGNITE-1:
Summary: Document IGNITE.CACHE_GROUPS view
Key: IGNITE-1
URL: https://issues.apache.org/jira/browse/IGNITE-1
Project: Ignite
Issue Type: Task
Alexey Goncharuk created IGNITE-:
Summary: Add verbose logging for node recovery
Key: IGNITE-
URL: https://issues.apache.org/jira/browse/IGNITE-
Project: Ignite
Issue Type: Ta
GitHub user a-polyakov opened a pull request:
https://github.com/apache/ignite/pull/5079
IGNITE-9990 Control.sh utility should request a password if necessary.
Signed-off-by: a-polyakov
You can merge this pull request into a Git repository by running:
$ git pull https://github
Hi, dear community,
1) I see dead link on the page
https://apacheignite-sql.readme.io/docs/jdbc-client-driver
Link "Cross-Cache Query"
https://apacheignite-sql.readme.io/docs/cache-queries#cross-cache-queries
points to 404 stub page. Could someone fix that?
2) I see it's a common problem.
Andrey,
I still see that checkpoint read lock acquisition raises a CRITICAL_ERROR,
which by default will shut down local node. As far as I remember, we
decided that by default thread timeout should not trigger node failure.
Now, however, it does, because we ignore SYSTEM_WORKER_BLOCKED events in
d
GitHub user gromtech opened a pull request:
https://github.com/apache/ignite/pull/5078
IGNITE-9937 Primary response error can be lost due to unwrapping a key
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5077
IGNITE-7164: SQL TX: Remap protocol
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7164
Alternatively you ca
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4821
---
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/5076
IGNITE-9171 Use lazy mode with results pre-fetch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9171
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5051
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4879
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4796
---
Github user xtern closed the pull request at:
https://github.com/apache/ignite/pull/5071
---
Hi Igor,
I'm not sure if someone in the community can know an answer to this
question.
I can share a page with resolved legal questions here:
https://www.apache.org/legal/resolved.html#category-b
But I think it may require confirmation from Apache Legal
http://www.apache.org/legal/
https://issue
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/5075
IGNITE-9988
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9988
Alternatively you can review and apply these
Alexei Scherbakov created IGNITE-9998:
-
Summary: .NET: Implement partition preload API
Key: IGNITE-9998
URL: https://issues.apache.org/jira/browse/IGNITE-9998
Project: Ignite
Issue Type:
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/5074
IGNITE-9622: MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ
transactions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/
Amelchev Nikita created IGNITE-9997:
---
Summary: IgniteDiagnosticMessagesTest.testLongRunningTx fails on TC
Key: IGNITE-9997
URL: https://issues.apache.org/jira/browse/IGNITE-9997
Project: Ignite
Alexey Goncharuk created IGNITE-9996:
Summary: Investigate possible performance drop in FSYNC mode for
ignite-2.7 compared to ignite-2.6
Key: IGNITE-9996
URL: https://issues.apache.org/jira/browse/IGNITE-9996
GitHub user xuchuanyin opened a pull request:
https://github.com/apache/ignite/pull/5073
IGNITE-9995: Fix bugs in windows launch bat script
Problems:
If user is under ignite source dir, launching ignite will cause "Input
line is too long" error. While if user switch to anothe
xuchuanyin created IGNITE-9995:
--
Summary: fix bugs
Key: IGNITE-9995
URL: https://issues.apache.org/jira/browse/IGNITE-9995
Project: Ignite
Issue Type: Improvement
Reporter: xuchuanyi
ARomantsov created IGNITE-9994:
--
Summary: idle_verify -analyze -partId= -grpId=(minus)number not
working
Key: IGNITE-9994
URL: https://issues.apache.org/jira/browse/IGNITE-9994
Project: Ignite
54 matches
Mail list logo
