Hi, Igniters.
I'd like to add new wiki page with suggestions for future Ignite 3.0
release. We can collect any ideas there and then discuss and refine them on
dev-list.
Could someone grant me (andrey-kuznetsov) write permission?
Hi Andrey,
I've updated permissions, please check.
Sincerely,
Dmitriy Pavlov
вт, 18 дек. 2018 г. в 12:34, Andrey Kuznetsov :
> Hi, Igniters.
>
> I'd like to add new wiki page with suggestions for future Ignite 3.0
> release. We can collect any ideas there and then discuss and refine them on
> d
I've created documentation ticket for UUID type - [1].
Now about Timestamp type. Binary protocol specification only specifies
how the data type should be transmitted by the network. The purpose and
main requirements for the protocol is to be compact and fast, it is not
designed to be used by user
Thanks, Dmitriy.
The page stub [1] is now created.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
Best regards,
Andrey Kuznetsov.
вт, 18 дек. 2018, 12:45 Dmitriy Pavlov dpav...@apache.org:
> Hi Andrey,
>
> I've updated permissions, please check.
>
> Sincerely
Stan,
In one of your emails you wrote why you need pre-touch:
> a) JVM doesn’t have to do it during the actual work (avoiding overhead for
> physical page allocation, possible contention with page cache, etc)
> b) JVM fails fast if the Xmx is greater than available RAM
> c) New processes will not
Igor Sapego created IGNITE-10728:
Summary: CPP: Move networking into separate library
Key: IGNITE-10728
URL: https://issues.apache.org/jira/browse/IGNITE-10728
Project: Ignite
Issue Type: Imp
Igor Seliverstov created IGNITE-10729:
-
Summary: MVCC TX: Improvements.
Key: IGNITE-10729
URL: https://issues.apache.org/jira/browse/IGNITE-10729
Project: Ignite
Issue Type: Improvement
Igor Seliverstov created IGNITE-10730:
-
Summary: MVCC TX: Batch WAL datarecords
Key: IGNITE-10730
URL: https://issues.apache.org/jira/browse/IGNITE-10730
Project: Ignite
Issue Type: Impro
Hi Zhenya,
Yes, will do in the nearest time.
On Sat, Dec 15, 2018 at 8:25 PM Zhenya Stanilovsky
wrote:
> i fill the ticket https://issues.apache.org/jira/browse/IGNITE-10654 ,
> Vladimir can u check it?
>
> thanks.
>
>
> >Суббота, 15 декабря 2018, 20:11 +03:00 от stanilovsky evgeny <
> estanil
Vitaliy Biryukov created IGNITE-10731:
-
Summary: ZookeeperDiscoverySpiTestSuite4:
IgniteCacheReplicatedQuerySelfTest.testNodeLeft fails
Key: IGNITE-10731
URL: https://issues.apache.org/jira/browse/IGNITE-10731
Hi folks,
During implementation of edge-chasing deadlock detection algorithm in
scope of [1] it has been realized that basically we have 2 options for
"chasing" strategy. I will use terms Near when GridNearTxLocal is
assumed and Dht when GridDhtTxLocal (tx which updates primary
partition). So, her
Folks,
Now I see 5-10% speedup at all TC suites right after the merge.
Great fix!
On Mon, Dec 17, 2018 at 2:39 PM Vyacheslav Daradur
wrote:
> Andrey Mashenkov, at first sight, I have not seen any problems with
> .NET platform.
>
> I believe we need carefully configure ports in platform's examp
Ivan,
I would prefer forward-only implementation even knowing it allows false
positive check results.
Why I think so:
1) From my experience, when we have any future is waiting for reply, we
have to take a failover into consideration.
Usually failover implementations are way more complex than an
Ilya Kasnacheev created IGNITE-10732:
Summary: Incorrect file.encoding leads to inconsistent
SqlFieldsQuery results between nodes
Key: IGNITE-10732
URL: https://issues.apache.org/jira/browse/IGNITE-10732
Both patches were applied. Maxim, thank you!
What about 1. An `Unexpected error during build messages processing in
TeamCity`, what can we do as the next step to fix it?
Sincerely,
Dmitriy Pavlov
пн, 17 дек. 2018 г. в 18:31, Andrey Mashenkov :
> Maxim,
>
> Looks ok. Let's apply IGNITE-10682.
>
Folks,
That's extremely awesome!
Now I see what stacktrace cause future creation and who will gain the
result and how.
Are there any chances to keep variable's values at original stacktrace?
Will this work correctly in case of concurrent calls?
for example, when more that one stacktrace will cau
Dmitry Konstantinov created IGNITE-10733:
Summary: CassandraStore in write behind mode loses data when
back-pressure is active
Key: IGNITE-10733
URL: https://issues.apache.org/jira/browse/IGNITE-10733
Hi Ivan,
To answer your last question, yes, all the tests are to be marked with @Test
annotations, and those that are meant to be ignored are going to be marked
with @Ignore annotations. There is no exceptions to that, and these
annotations will work just as well on tests using our home brewed
bef
Evgenii Zhuravlev created IGNITE-10734:
--
Summary: Add documentation for the list of operations that should
be retried in case of cluster topology changes
Key: IGNITE-10734
URL: https://issues.apache.org/jira/
Ilya Borisov created IGNITE-10735:
-
Summary: Web console: use rxjs EMPTY instead of empty
Key: IGNITE-10735
URL: https://issues.apache.org/jira/browse/IGNITE-10735
Project: Ignite
Issue Type:
Alexander Kalinin created IGNITE-10736:
--
Summary: Update tabs in
Key: IGNITE-10736
URL: https://issues.apache.org/jira/browse/IGNITE-10736
Project: Ignite
Issue Type: Improvement
21 matches
Mail list logo
