[
https://issues.apache.org/jira/browse/SOLR-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232283#comment-17232283
]
bai sui commented on SOLR-15000:
--------------------------------
TO：David
Thank you very much for your timely reply to my issue at the weekend
1）as you said “Community building is hard!”，I very much agree. Since leaving my
last company in 2015, I have been focusing on building an enterprise
application search platform and developing it on my own. Address is:
[https://github.com/qlangtech/tis-solr|https://github.com/qlangtech/tis-solr].
It may be because there is not enough communication with the community, so
there are not many users, so that there is no contributor to participate. It
seems that there is still a gap with the requirements of the ASF incubation
project. So, next I need to strengthen the construction of the community.
2) Thank you very much for telling me so many excellent projects, such as fess,
Chorus, awesome-search, it seems that I am really lonely, I need to spend some
time to learn about them.
3) Your suggestion is correct, *take all of the great parts of TIS, and maybe
contribute to existing projects*. Next, I will consider this matter and feed
back some good features in TIS to the community.
4) Regarding the fourth point, I have some ideas of my own. I think the reason
for Elasitc's success is that Elasitc uses the user's perspective to visualize
time series data as a breakthrough, and uses the ELK tool stack to firmly
attract users. I think users are lazy, and users don't care if your product is
"rolling a full application stack", don't you think?
It may be that what I said is different from what you said. What you said is
*project*, but what I said is *product*.
tks so much for your replying
> Solr based enterprise level, one-stop search center products with high
> performance, high reliability and high scalability
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-15000
> URL: https://issues.apache.org/jira/browse/SOLR-15000
> Project: Solr
> Issue Type: Wish
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Reporter: bai sui
> Priority: Minor
> Attachments: add-collection-step-2-expert.png,
> add-collection-step-2.png
>
>
> h2. Summary
> I have developed an enterprise application based on Solr，named TIS . Use TIS
> can quickly build enterprise search service for you. TIS includes three
> components:
> - offline index building platform
> The data is exported from ER database( mysql, sqlserver and so on) through
> full table scanning, and then the wide table is constructed by local MR tool,
> or the wide table is constructed directly by spark
> - incremental real-time channel
> It is transmitted to Kafka , and real-time stream calculation is carried out
> by Flink and submitted to search engine to ensure that the data in search
> engine and database are consistent in near real time
> - search engine
> currently，based on Solr8
> TIS integrate these components seamlessly and bring users one-stop, out of
> the box experience.
> h2. My question
> I want to feed back my code to the community, but TIS focuses on Enterprise
> Application Search, just as elasitc search focuses on visual analysis of time
> series data. Because Solr is a general search product, *I don't think TIS can
> be merged directly into Solr. Is it possible for TIS to be a new incubation
> project under Apache?*
> h2. TIS main Features
> - The schema and solrconfig storage are separated from ZK and stored in
> MySQL. The version management function is provided. Users can roll back to
> the historical version of the configuration.
> !add-collection-step-2-expert.png|width=500!
> !add-collection-step-2.png|width=500!
> Schema editing mode can be switched between visual editing mode or
> advanced expert mode
> - Define wide table rules based on the selected data table
> - The offline index building component is provided. Outside the collection,
> the data is built into Lucene segment file. Then, the segment file is
> returned to the local disk where solrcore is located. The new index of reload
> solrcore takes effect
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
