I am trying to explore the extensibility of Apache Ignite 2.7 in terms of
security configuration.
In particular, ability to modify the authentication structure and
implement
a specific kerberos mechanism in:
-Zookeeper Discovery
-Internode communication
Hi,
Regarding 2.7.5. But why do you treat it as a "half before 2.8.0"? I
think it is just Java 9+ support, isn't it?
ср, 20 мар. 2019 г. в 14:02, Anton Vinogradov :
>
> >> And I hope Anton will guide me if I'll be stuck somewhere.
> I will :)
>
> On Wed, Mar 20, 2019 at 1:42 PM Dmitriy Pavlov wr
Pavel Vinokurov created IGNITE-11585:
Summary: Update Spring dependency to version 5
Key: IGNITE-11585
URL: https://issues.apache.org/jira/browse/IGNITE-11585
Project: Ignite
Issue Type:
Hello!
I would like to contribute to apache ignite and i am asking for
contribution permission.
I would like to start with IGNITE-10997.
My github username: denis-chudov
Jira username: Denis Chudov
--
Denis Chudov
Software Engineer, Moscow
+7 905 5775239
https://www.gridgain.com
Powered by Apache®
I think that we as the community should consider discontinuing the
full-text search support. It goes with many limitations and not widely
used. The market is flooded with many products designed for full-text
search scenarios.
-
Denis
On Wed, Mar 20, 2019 at 3:44 AM Dmitriy Pavlov wrote:
> +1 f
Hi, is there any reason why you can't use ElastiSearch or similar products
designed for full-text search use cases?
-
Denis
On Wed, Mar 20, 2019 at 2:51 AM Andrey Mashenkov
wrote:
> Hi,
>
> No, due to H2 limitation.
> H2 allow user define Function as a table, but seems an additional support
>
Pavel Pereslegin created IGNITE-11584:
-
Summary: Implement batch insertion of new cache entries in
FreeList to improve rebalancing
Key: IGNITE-11584
URL: https://issues.apache.org/jira/browse/IGNITE-11584
Hi Ignite Developers,
In a separate discussion, I've shared a log with all commits.
As far as I can see, nobody removed commits from this sheet, so the scope
of release will be discussed in another way: only explicitly declared
commits will be cherry-picked.
Sincerely,
Dmitriy Pavlov
Dear Ignite Developer,
Branch Ignite 2.7.5 created for half release. This release (and branch) is
based on 2.7:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=shortlog;h=refs/heads/ignite-2.7.5
See more info
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
TC bot will be s
Max Shonichev created IGNITE-11583:
--
Summary: Seems that copypasted code from ignite.sh is irrelevant
in control.sh
Key: IGNITE-11583
URL: https://issues.apache.org/jira/browse/IGNITE-11583
Project:
Hi Igniters!
I have a questions according to beforeTest(s)/afterTest(s) methods. I tried
to make them correspond to JUnit 4+ semantics in the context of iep30 [1].
And I see there two solutions:
1. Place test scenario under the Rule annotation as it has already done in
GridAbstractTest [2]. It is
I've removed debated line from the document. As we don't have consensus on
lazy consensus it is better to start a separate discussion for this topic.
I prefer to build consensus here while procedural changes do not require it
and Majority Approval is enough.
We time to time use lazy consensus, so
Hi, probably questions related to features support/functioning/plans it
better to ask using u...@ignite.apache.org because all other subscribed
users can see an answer.
Dev. list intended for discussing contributions-related questions, e.g. if
someone wants to support any kind of new feature/fix b
Alexey Platonov created IGNITE-11582:
Summary: [ML] Pipelines should work with Vectorizers
Key: IGNITE-11582
URL: https://issues.apache.org/jira/browse/IGNITE-11582
Project: Ignite
Issue
Hello, Igniters!
I found a bug with handling events when the client reconnects.
Discovery has a queue for events. It's processed by event thread. If
we hold up event processing using a listener on the client side and
restarts cluster - the client will reconnect. After it reconnects it
will contin
Alexey Platonov created IGNITE-11580:
Summary: [ML] Evaluators should accept Vectorizers
Key: IGNITE-11580
URL: https://issues.apache.org/jira/browse/IGNITE-11580
Project: Ignite
Issue Ty
>> And I hope Anton will guide me if I'll be stuck somewhere.
I will :)
On Wed, Mar 20, 2019 at 1:42 PM Dmitriy Pavlov wrote:
> +1 for 2.7.5 because it has at least meaningful reasoning behind it (2.7.5
> = half release before 2.8.0).
>
> If no one else wants to be a release manager, I will try
Alexey Platonov created IGNITE-11581:
Summary: [ML] Adapt tutorial to new vectorizer API
Key: IGNITE-11581
URL: https://issues.apache.org/jira/browse/IGNITE-11581
Project: Ignite
Issue Ty
+1 for keeping indexes as is. Moreover, sorry for off-topic Lucene is not
modular (Jigsaw-compliant), and having this dependency in ignite-indexing
make this jar also Java module - incompliant.
ср, 20 мар. 2019 г. в 13:15, Maxim Muzafarov :
> Hello,
>
> The link [1] is the issue with Persistence
+1 for 2.7.5 because it has at least meaningful reasoning behind it (2.7.5
= half release before 2.8.0).
If no one else wants to be a release manager, I will try to do it. And I
hope Anton will guide me if I'll be stuck somewhere.
ср, 20 мар. 2019 г. в 13:04, Anton Vinogradov :
> 2.7.42?
> 2.7.1
Eduard Shangareev created IGNITE-11579:
--
Summary: Add new commands to deal with garbage in partitions which
left after cache destroy in shared cache groups
Key: IGNITE-11579
URL: https://issues.apache.org/jir
Hello,
The link [1] is the issue with Persistence for text indices.
AFAIK, the issue is very difficult with their implementation and has a
doubtful performance improvement. One of the most obvious
disadvantages of persisted Lucene indexes can be that they will
dramatically slow down the node star
Eduard Shangareev created IGNITE-11578:
--
Summary: Stopping node after destroying cache in shared cache
group would leave data of this cache in persistence
Key: IGNITE-11578
URL: https://issues.apache.org/jira
2.7.42?
2.7.100500?
Let's just keep 2.7.3.
On Wed, Mar 20, 2019 at 1:00 PM Ilya Kasnacheev
wrote:
> Hello again!
>
> Sorry for spam, but if our main feature is Java 11 support, why not call it
> 2.7.11? :)
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 20 мар. 2019 г. в 12:58, Ilya Kasnacheev :
Hello again!
Sorry for spam, but if our main feature is Java 11 support, why not call it
2.7.11? :)
Regards,
--
Ilya Kasnacheev
ср, 20 мар. 2019 г. в 12:58, Ilya Kasnacheev :
> Hello!
>
> Minor nitpick, why not 2.7.5 then?
>
> 2.7.3 is a kind of version that you want to hear more of its story
Hello!
Minor nitpick, why not 2.7.5 then?
2.7.3 is a kind of version that you want to hear more of its story.
However, releasing a "half releases" of N.5 is a very old tradition in
software, when there are more changes than in a minor fix but not enough to
increment N.
Regards,
--
Ilya Kasnache
Hi,
No, due to H2 limitation.
H2 allow user define Function as a table, but seems an additional support
needed from Ignite side.
AFAIK there is no plan to add such support for now.
Feel free to create a ticket for this.
On Wed, Mar 20, 2019 at 9:16 AM Tâm Nguyễn Mạnh
wrote:
> Hi Igniters,
>
>
Hello!
- Lucene indexes are not persistent and there are currently no plans to
make them persistent.
- I could say more about that ticket have you actually linked to it.
Regards,
--
Ilya Kasnacheev
ср, 20 мар. 2019 г. в 09:23, Tâm Nguyễn Mạnh :
> Hi Igniters,
>
> Since Ignite have native pers
28 matches
Mail list logo
