I've got your point Val, thanks. At least we can consider this issue
during Ignite 3 development.
03.06.2021 19:10, Valentin Kulichenko пишет:
Folks,
This is a usability issue of the current API, which I don't think we can
easily fix right now without breaking compatibility.
There are two
hello,
can someone can help to merge the following patch into master?
https://issues.apache.org/jira/browse/IGNITE-12852
This patch has been completed for a long time, and I think it is a
valuable one.
在 2021/6/3 下午11:12, Dmitry Pavlov 写道:
Sure, thanks for your reply
Folks, could you
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Alexei, In general I agree with the given proposal.
However I'd also like to clarify a few things:
1. start() is called in "depends on" relation order.
2. It might have sense to add a runLevel parameter to start(): start(int
runLevel).
3. Seems that we don't need an afterStart() method. Cause we
Sure, thanks for your reply
Folks, could you please advice how to setup JIRA account integration for
non-committers?
For the page
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11
I can see all issues, but Alexey's login seems to be not sufficient. Can wiki
admins set up
I mean I'm OK to release it with 2.12. So, I am glad to hear there are
chances for 2.11, but I guess we can postpone it.
On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov wrote:
> ok, Maksim, keep us posted.
>
> We're in the middle of paperwork rigth now, so there is a chance ))
>
> On 2021/06/03
I've made a small mistake above, the correct sentence is
void stop(); // Stop a component. Invoked in "depends on" relation order.
In the example above, RaftGroup is stopped before the Network.
чт, 3 июн. 2021 г. в 17:36, Alexei Scherbakov :
> Sergey, I'm ok with the runlevel approach.
>
>
ok, Maksim, keep us posted.
We're in the middle of paperwork rigth now, so there is a chance ))
On 2021/06/03 14:30:55, Maksim Timonin wrote:
> > Regarding non-SQL index API it really depends on readiness. I guess if it
> is not in the master, we can skip and release it next time.
>
> Hi,
Sergey, I'm ok with the runlevel approach.
I've thought about the node/components lifecycle, here my ideas:
1. The Component interface.
Each manageable component must implement it.
2. Define components hierarchy.
Each component can depend on others - this produces component hierarchy
defined by
> Regarding non-SQL index API it really depends on readiness. I guess if it
is not in the master, we can skip and release it next time.
Hi, Dmitry! Yes, currently it is on review. I'm OK to release it within the
next release.
On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov wrote:
> Hi Alexey,
>
>
Hi Alexey,
Releasing master as-is makes sence for me.
Regarding non-SQL index API it really depends on readiness. I guess if it is
not in the master, we can skip and release it next time.
We've a bit overdue initial scope freeze date. It's not a big deal, but still
makes sense to start
:scope:
Here is a list [1] of 195 tickets, i picked for Apache Ignite 2.11 release
Let's start discussion
[1]
Hi Sergey,
Sounds interesting, I do agree that it might be beneficial to improve the
lifecycle management in 3.0 - 2.x version is far from perfect.
Regarding your questions:
1. Can this be done via the metastore?
2. I think we should list the run levels that we think should be there, and
then
Folks,
This is a usability issue of the current API, which I don't think we can
easily fix right now without breaking compatibility.
There are two separate cases.
First - the value class is a user's POJO. This one is straightforward - we
analyze annotations and create indexes based on that. The
Checked, it's ok. Thank you.
On 2021/06/03 08:27:07, Dmitry Pavlov wrote:
> Alexey,
>
> I've granted you edit permissions.
> Please check availability.
>
> Sincerely,
> Dmitriy Pavlov
>
> On 2021/06/03 08:24:03, ��
> wrote:
> > My login is: agidaspov
> >
Hi, Ilya.
Could you please provide a reproducer of wrong behavior? Looks like I'm
missing smth in your idea. There is my code [1] with String class as value,
and TextQuery works correctly without the annotation QueryTextField. And I
expect this behavior.
> case of plane strings as cache values
Alexey,
I've granted you edit permissions.
Please check availability.
Sincerely,
Dmitriy Pavlov
On 2021/06/03 08:24:03, ��
wrote:
> My login is: agidaspov
> E-mail: olive.c...@gmail.com
>
> On 2021/06/03 08:17:15, Dmitry Pavlov wrote:
> > Can you please sign
My login is: agidaspov
E-mail: olive.c...@gmail.com
On 2021/06/03 08:17:15, Dmitry Pavlov wrote:
> Can you please sign in to cwiki and share your login?
>
> wiki admins (PMC members) could grant access in that case.
>
> On 2021/06/03 07:11:54, Алексей Гидаспов wrote:
> > Hi, Igniters!
> >
Can you please sign in to cwiki and share your login?
wiki admins (PMC members) could grant access in that case.
On 2021/06/03 07:11:54, Алексей Гидаспов wrote:
> Hi, Igniters!
>
> As a release manager of 2.11 Apache Ignite release I need edit access to
> cwiki.apache.org Apache Ignite space.
Thanks for feedback Maksim, but let me disagree with you.
As far as i understand
CacheConfiguration.setIndexedTypes(Long.class, String.class);
Is just the hint for Ignite about data that should be indexed, but what
kind of index should be created depends on our configuration. For example:
Hi, Igniters!
As a release manager of 2.11 Apache Ignite release I need edit access to
cwiki.apache.org Apache Ignite space. Please tell me, how can I obtain it?
22 matches
Mail list logo
