I have a couple. After a while you get the feel for your own. So, here is a couple of basic examples:
1.1) I created a saved filter called "All open Solr issues": project = SOLR AND status in (Open, "In Progress", Reopened) 1.2) I created a dashboard widget with HeatMap type, using that filter as base and Statistics Type of "Raised in Versions (all)". This gives me quick links to still open issues originally reported against specific Solr versions. So, you can start from the oldest and keep going until you find one you feel comfortable with. 2.1) I created a saved filter for all open issues with attachments that haven't been touched for a while: project = SOLR AND issuetype = Bug AND status in (Open, "In Progress", Reopened) AND "Attachment count" >= "1" AND "Last public comment date" <= -30d 2.2) I created a heatmap widget with that filter and breakdown by "Fix for versions (all)". This gives me issues that may have patches (though could be screenshots, etc) that may be worth trying to reproduce as somebody obviously spent time on them already. 3.1) I created a saved filter for all issues in SOLR (of any status): project = SOLR 3.2) I created widget with "Two dimensional filter statistics" based on that filter and Status as XAxis, Components as YAxis, sorted by total descending. This gives me issues tagged with specific components and links to their status breakdowns. This allows you to pick an interesting area and dig in that way. This is the basic pattern of my operation. I create a filter that shows the issues I am curious about (think of it as Solr fq filters) and then I apply various breakdowns to identify most relevant sub-segments (think of it as facets) within them. And then I actually do the work (well did when I had more free time). Good luck, Alex. ---- http://www.solr-start.com/ - Resources for Solr users, new and experienced On 6 November 2017 at 04:40, manish kakoti <[email protected]> wrote: > Hi Alexandre, > > Thank you for your valuable suggestion, Yes that is definitely a great > starting point. It would very helpful if you can add the link for the old > JIRA issues that you have mentioned. > > Regards > Manish Kakoti > > On Sun, Nov 5, 2017 at 11:01 PM, Alexandre Rafalovitch <[email protected]> > wrote: >> >> Two things I want to add that I swore were in the guide, but can't >> easily see them. >> >> The first is triaging old JIRA issues. It is very valuable to be able >> to pick up old JIRA issues (opened against Solr 1.x, 2.x, 3.x, 4.x or >> even 5.x) and testing them against the latest release to see if the >> issue is still present or not. Often, they are no longer relevant, >> have been fixed or have not enough details to even figure out what the >> issue is. Adding a quick note to Jira for that, would help somebody >> else with the privileges to then resolve/close/mark-duplicate on the >> issue. And, you will learn a lot in the process of trying to figure >> out whether the issue is still present or not. I speak from personal >> experience here. If you do choose this path, let me know and I will >> share JIRA queries I used to quickly identify potential issues to >> review. >> >> Also, testing anything on Windows would be very helpful. Examples, >> Readme instructions, shipped extra libraries, etc. Most of the >> developers are not using Windows, so that's a bit of a dusty corner. >> And dusty corner with strange edge-case bugs around spaces, quotes, >> command line parameters and like. And yet again, doing this will give >> you cross-cutting understanding of Lucene/Solr, its various components >> and how they interact together. >> >> Regards, >> Alex. >> >> >> ---- >> http://www.solr-start.com/ - Resources for Solr users, new and experienced >> >> >> On 5 November 2017 at 04:43, Erick Erickson <[email protected]> >> wrote: >> > See: https://wiki.apache.org/solr/HowToContribute for both suggestions >> > on the kinds of things you could contribute (code isn't the only way!) >> > >> > After that, pick something specific that interests you. Are you a UI >> > wizard and would like to improve the admin UI? Want to grab a test >> > failure case and see if you can understand the root cause and fix it? >> > Tell us what you're interested in/skilled at and maybe we can give you >> > a first project. >> > >> > After that, you have to jump in and dig. If you want to start with the >> > code, check out the project (the link above will tell you how) and get >> > it compiling and set up in your IDE of choice, IntellIJ and Eclipse >> > are the most popular amongst the developers... >> > >> > And if you do want to work with the actual code, I'd dive into some >> > problem (see the JIRA list or failing tests) _and_ discuss the >> > approach you want to take after you've explored for a while. IOW, >> > don't think you need to have a solution before asking questions! >> > >> > Best, >> > Erick >> > >> > On Sat, Nov 4, 2017 at 7:01 AM, Shashank Tyagi >> > <[email protected]> wrote: >> >> +1 >> >> >> >> >> >> On Sat, Nov 4, 2017 at 4:08 PM, manish kakoti >> >> <[email protected]> >> >> wrote: >> >>> >> >>> Hello, >> >>> >> >>> I am new to Lucene, and i am really interested to contribute to >> >>> it.How do >> >>> i actually get started with it? >> >>> Could use some suggestions and support in order to get started with >> >>> it. >> >>> >> >>> Regards >> >>> Manish Kakoti >> >> >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
