I assume this project is dead? #33
Comments
|
Well, we are not making fresh commits as the newer versions of Liferay(7+)
have elasticsearch support inbuilt. But there is a very large installed
base of older Liferay versions (6.x) which will benefit from elasticray. We
keep seeing downloads/usage/emails from large cos./orgs from Europe and
Americas. This works flawlessly in 6.x versions and there are no outstanding addressable bugs. Hence no commits.
Also see elasticray.com
Is there a reason on why you are checking if the project is dead? Will
there be any github action if it does not see activity ?
Hope you are not deleting the project. Please let me know if it so and I
will make a local copy of the code.
Thanks,
kc
K.C.Ramakrishna
in.linkedin.com/pub/ramakrishna-kc/2/2a/864/
www.rknowsys.com
…On Wed, Aug 8, 2018 at 11:19 AM, bitsofinfo ***@***.***> wrote:
I assume this project is dead?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#33>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAF8DxgMTvB_Zg6tGnyEk5e9jeSog2pHks5uOnv-gaJpZM4VzUGq>
.
|
|
Well elasticsearch is now on version 6, with 7 coming soon. This appears to have been developed working against ES 1.3.x and maybe 2.x? I need to know are there any plans to make this function with elasticsearch 6.x? ES 1.3 and 2.x are old.
Huh?!? |
|
On Wed, Aug 8, 2018 at 11:31 AM, bitsofinfo ***@***.***> wrote:
Well elasticsearch is now on version 6, with 7 coming soon. This appears
to have been developed working against ES 1.3.x and maybe 2.x?
Yeah. We did work a bit on upgrading to latest version of elastic but it
got a bit complicated and our day jobs are not allowing us enough time.
I need to know are there any plans to make this function with
elasticsearch 6.x? ES 1.3 and 2.x are old.
Not plans at this moment.
Huh?!?
My mistake. For some reason I assumed you were a github admin. Ignore it.
|
|
So we'd really like to use this, but we use more recent versions of elasticsearch... i mean 1.3.x is so old. So there are no plans to upgrade support? |
|
We do have commercial support options. Can you please email me on kcr at
rknowsys dot com ?
Thanks,
kc
K.C.Ramakrishna
+91-98494-16664
in.linkedin.com/pub/ramakrishna-kc/2/2a/864/
www.rknowsys.com
…On Wed, Aug 8, 2018 at 3:05 PM, bitsofinfo ***@***.***> wrote:
So we'd really like to use this, but we use more recent versions of
elasticsearch... i mean 1.3.x is so old.
So there are no plans to upgrade support?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAF8DzioWslHmoERIKs4V1QaXEhJ8YIpks5uOrDwgaJpZM4VzUGq>
.
|
|
Can you please post that information here |
|
I meant a specific one time consulting engagement (hourly rate) to ensure
that we make it compatible for your version of Liferay and Elastic. We are
primarily a FOSS consulting/development firm - www.rknowsys.com and were
consulting on Liferay and when we saw elastic, we thought it was pretty
cool and developed elasticray (on our own time) to help our client move
from SOLR to Elastic.
We estimate ~ 10-20 hrs of work for each combination of liferay<>elastic
version - we can do this for the specific versions that you want. Once we
get your version working, we can do incident based support (but doubt that
you need it - most installations we know are running without issues for
long periods). Obviously would not want to discuss consulting commercials
on a public forum.
We of course have a lot of expertise on Liferay too (~ developing on
Liferay since 2008) and Elastic (since 2015) and will be more than happy to
help you with Liferay, Java, elastic, Hadoop, Spark, R (more on
www.rknowsys.com) development and consulting too.
Please do reach out to me on kcr at rknowsys dot com for
consulting/development rates.
Best Regards,
kc
K.C.Ramakrishna
+91-98494-16664
in.linkedin.com/pub/ramakrishna-kc/2/2a/864/
www.rknowsys.com
…On Wed, Aug 8, 2018 at 4:03 PM, bitsofinfo ***@***.***> wrote:
Can you please post that information here
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAF8D3BKSRZgK-m10YXEPl3K9nBEn3oXks5uOr6DgaJpZM4VzUGq>
.
|
|
Understood, might just fork and make the necessary changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I assume this project is dead?
The text was updated successfully, but these errors were encountered: