[jira] [Commented] (SOLR-15000) Solr based enterprise level, one-stop search center products with high performance, high reliability and high scalability

["David Eric Pugh (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232023#comment-17232023 ] 

David Eric Pugh commented on SOLR-15000:
----------------------------------------

Congrats on opening a JIRA ticket with a great number, 15000!   

I wanted to share a couple of thoughts, because I suspect that you are right that TIS, as it stands, wouldn't make sense as part of Apache Solr.  

1) As far as the Incubator goes, go through the http://incubator.apache.org/cookbook/ and evaluate if it's a process worth embracing.  It's not an insignificant, and thats intentional.  ASF wants to grow and build new communities, not become a repository for abandoned projects.  Community building is hard!    I suspect, that if you can build a basic community around TIS outside of the ASF, you will find it easier to join the Incubator program.

2) As a follow on to #1, think about how to raise the profile of TIS.  Do you have regular updates and public releases?   Do you have active contributors from multiple organizations?   Is there evangelism you can do with TIS to get there?   For example, make sure that TIS has nice docs and website, and get it added to https://github.com/frutik/awesome-search so people see it.  Start tweeting about it ;-).   A model to look at is Fess (https://github.com/codelibs/fess), which is somewhat similar to TIS ;-).  Also, check out what I'm doing with Chorus, a ecomm focused stack based on Solr: https://github.com/querqy/chorus.   To build community there, we're starting a series of workshops to teach people how to use Chorus, get folks excited about it, and build some momentum.  https://plainschwarz.com/ps-salon/.  Obviously, the Chorus effort is going to be a multiyear effort that consumes a lot of my energy, and that's probably what you should plan on for TIS if you want to go this route!

3) An alternative path might be to take all of the great parts of TIS, and maybe contribute to existing projects.  For example, your schema editing stuff sounds cool, maybe you could partner up with https://github.com/yasa-org/yasa project to push forward on that?  Or, if you enjoy old Angular code, maybe submit PR's to existing Solr Admin to add that there ;-).

4) Another idea is that instead of rolling a full application stack, which honestly would be daunting for someone to jsut adopt wholesale, leverage all the new Package stuff in Solr to make Packages that run with Solr 8...   Create some good packages, submit them to http://solr.cool, and look to get adoption that way.  

Hope this helps!


> 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: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org