Re: [hibernate-dev] A warmup task: HSEARCH-2207

[Gunnar Morling]

Hey Mincong,

Nice! Looking forward to your pull request for this issue very much.

Thanks,

--Gunnar



2016-04-13 1:32 GMT+02:00 Sanne Grinovero :

> Hi Mincong,
> great start!
>
> I've added you to the right groups on JIRA, so now HSEARCH-2207 is
> assigned to you.
>
> To be allowed to send emails to the hibernate dev mailinst list you
> have to register first:
>   - https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
> Thanks,
> Sanne
>
>
> On 12 April 2016 at 22:55, Mincong Huang  wrote:
> > Hi Sanne ant Gunner,
> >
> > Concerned with the issue HSEARCH-2207, I'm studying on it.
> >
> > I created a demo and write a blog about boolean query in Apache Lucene.
> > As for Hibernate Search, I still not start learning it. I'll probably
> start
> > this weekend.
> > For instant, my priority is to understand the index, query and analyzer
> in
> > Lucene.
> >
> > My JIRA account is mincon...@gmail.com
> >
> > I'm not allowed to send email to hibernate dev list, so it isn't in cc.
> >
> > Cheers,
> > Mincong
> >
> >
> >
> >
> > On Sat, Apr 9, 2016 at 8:27 PM, Mincong Huang 
> wrote:
> >>
> >> Hi Sanne,
> >>
> >> Thanks for your email. No, it won't be boring at all. On the contrary,
> >> this will be a great beginning !
> >> I'll take a look on the issue and keep you informed. As for the JIRA
> >> account, here's the mine :
> >> mincon...@gmail.com
> >>
> >> Cheers,
> >> Mincong
> >>
> >>
> >> On Fri, Apr 8, 2016 at 2:35 PM, Sanne Grinovero 
> >> wrote:
> >>>
> >>> Hi Mincong,
> >>>
> >>> Gunnar suggested that I find a first task for you to familiarize with
> >>> the project, and to have you practice the process of creating patches
> >>> and proposing them for integration over GitHub.
> >>>
> >>> I think this issue could be suited:
> >>>  - https://hibernate.atlassian.net/browse/HSEARCH-2207
> >>>
> >>> I hope it's not too boring! It's not just an exercise, we need that
> >>> done so it would be a valuable contribution already.
> >>>
> >>> Do you have an account on our JIRA server? If not create one, then let
> >>> me know your user id so I can assign the issue to you.
> >>>
> >>> Thanks,
> >>> Sanne
> >>
> >>
> >
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] GitHub PR management

[Vlad Mihalcea]

Hi,

I went through all PR and applied labels on all items.

This way it's much easier to start reviewing issues because they are
categorized.

Let me know what you think.

Vlad

On Tue, Apr 12, 2016 at 5:08 PM, andrea boriero 
wrote:

> +1
>
> On 12 April 2016 at 14:56, Vlad Mihalcea  wrote:
>
>> Hi,
>>
>> Both Andrea and I have been going through the current list of PR, and I
>> think it is a good idea to start labeling them.
>> Some issues are trivial and can be integrated as soon as we can commit on
>> the master.
>>
>> I think we should add the following labels:
>>
>> - Needs CLA
>> - Needs Jira
>> - Needs Test Case
>> - Envers
>> - 4.2
>> - 4.3
>> - 5.0
>> - 5.1
>>
>> This way we can easily navigate through them.
>>
>> Vlad
>> ___
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] PR without CLA

[Vlad Mihalcea]

Hi,

I managed to get a list of PR without CLA. I asked them if they signed it,
but didn't get any response back.
Steve, if you can check them in the system, I'll update the PR status for
the ones that have signed the agreement.

https://github.com/hibernate/hibernate-orm/labels/Requires%20CLA

Otherwise, what shall we do with all those PRs?

Vlad
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] [HSEARCH] Scope of the first version with ES support

[Gunnar Morling]

Hey,

I'd like to achieve clarity and agreement on the scope of HSEARCH 5.6, the
first release with support for the Elasticsearch indexing backend.

I suggest we limit ourselves to the essential things making the backend
actually usable and release it as a "technology preview" as of 5.6.0.Final.
Everything not needed for that goal I'd move to subsequent releases (5.7,
6.0), the motivation being that we should not kill the vibe and deliver
something real soon.

Some candidates for moving over I see:

* "Define analyzers via the REST API (HSEARCH-2219
)": Users can create
the needed analyzers themselves
* "Consider using the fields feature of Elasticsearch for properties mapped
on several fields" (HSEARCH-2215
): Seems scheduled as
a "reminder" only anways?
* "Use the Elasticsearch Scroll API when fetching large result sets" (
HSEARCH-2128 ): Seems
not strictly needed
* "Map the optimize() operation to Elasticsearch 'force merge' requests" (
HSEARCH-2092 ): Manual
requests possible as a work-around
* Likely some others

Things we *should* do are most mapping-related issues, documentation and
apparent perf issues (massing indexing, avoid too frequent refreshing).

The public interest in the subject seemed good, so I'd prefer if we can
ship a "Final" version soon in MVP-style. As it seems, a "final" tech
preview is less scary to people than an Alpha/Beta. Let's hone the bits it
in subsequent releases, rather than working on the first Final for a long
time.

Any thoughts?

--Gunnar
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev