[
https://issues.apache.org/jira/browse/JAMES-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier closed JAMES-3266.
---
Resolution: Fixed
> Distributed James: make ElasticSearch indexing optio
] contributed to disable ES
in distributed James
> Distributed James: make ElasticSearch indexing optional?
>
>
> Key: JAMES-3266
> URL: https://issues.apache.org/jira/browse/JAMES-3266
>
Benoit Tellier created JAMES-3266:
-
Summary: Distributed James: make ElasticSearch indexing optional?
Key: JAMES-3266
URL: https://issues.apache.org/jira/browse/JAMES-3266
Project: James Server
Hi,
I've looking again at this thread and I see strong arguments over a
technical issue.
The proposal in question is whether we should add a configuration switch
to OPT-IN/OUT of a large, useful dependency.
This is a technical decision that has implications mostly for users and
less for
Hi,
On Wed, 2020-06-17 at 17:53 +0200, Raphaël Ouazana-Sustowski wrote:
> Hi Matthieu,
>
> I don't see much new arguments in your last answer.
It's weird because I think I didn't really repeat what I said
previously.
> I can answer your
> questions one by one, but I would like to go forward.
Hi Matthieu,
I don't see much new arguments in your last answer. I can answer your
questions one by one, but I would like to go forward.
Would it make a consensus for you if we work on merging the current PR,
with always the option to revert it and go to a product if needed?
Or do you
On Mon, 2020-06-15 at 15:30 +0200, Raphaël Ouazana-Sustowski wrote:
>
[...]
> > > I see many use cases where you would not need search, essentially
> > > based
> > > on automatic mail processing, which is a common James workflow.
> > Does it still make sense to support IMAP at this point? I'm
Hello,
Le 15/06/2020 à 09:52, Matthieu Baechler a écrit :
Hi Raphael,
On Fri, 2020-06-12 at 18:29 +0200, Raphaël Ouazana-Sustowski wrote:
Hello Matthieu,
Le 12/06/2020 à 10:05, Matthieu Baechler a écrit :
Hi Raphael,
My answers below
On Thu, 2020-06-11 at 18:01 +0200, Raphaël
Hi Raphael,
On Fri, 2020-06-12 at 18:29 +0200, Raphaël Ouazana-Sustowski wrote:
> Hello Matthieu,
>
> Le 12/06/2020 à 10:05, Matthieu Baechler a écrit :
> > Hi Raphael,
> >
> > My answers below
> >
> > On Thu, 2020-06-11 at 18:01 +0200, Raphaël Ouazana-Sustowski wrote:
> > > Hi,
> > >
> > >
Hello Matthieu,
Le 12/06/2020 à 10:05, Matthieu Baechler a écrit :
Hi Raphael,
My answers below
On Thu, 2020-06-11 at 18:01 +0200, Raphaël Ouazana-Sustowski wrote:
Hi,
Here is a proposal to make ElasticSearch optional in our distributed
product/flavor/server.
Comments are welcome.
##
Hi Raphael,
My answers below
On Thu, 2020-06-11 at 18:01 +0200, Raphaël Ouazana-Sustowski wrote:
> Hi,
>
> Here is a proposal to make ElasticSearch optional in our distributed
> product/flavor/server.
>
> Comments are welcome.
>
>
> ## Why?
>
> Some people have expressed the need of using
+1
Making complexity OPT-IN is a nice touch.
La 12.06.2020 05:06, Tellier Benoit a scris:
> +1
>
> On 11/06/2020 23:01, Raphaël Ouazana-Sustowski wrote:
>> Hi,
>>
>> Here is a proposal to make ElasticSearch optional in our distributed
>> product/flavor/server.
>>
>> Comments are welcome.
>>
>>
+1
On 11/06/2020 23:01, Raphaël Ouazana-Sustowski wrote:
> Hi,
>
> Here is a proposal to make ElasticSearch optional in our distributed
> product/flavor/server.
>
> Comments are welcome.
>
>
> ## Why?
>
> Some people have expressed the need of using a distributed James without
>
Hi,
Here is a proposal to make ElasticSearch optional in our distributed
product/flavor/server.
Comments are welcome.
## Why?
Some people have expressed the need of using a distributed James without
ElasticSearch:
- in some comment here: https://issues.apache.org/jira/browse/JAMES-3086
-
14 matches
Mail list logo
