Janusman has more notes on this, so I hope he'll add to it.

We had a BoF and many discussion at Drupalcon, here's the take away:

  • Abandon any attempt to keep the schema in sync with 6.x-1.x and remove most or all node-specific fields. Mostly done at #1088208: Simplfy schema.xml to use more dynamic fields
  • get some Views integration asap (volunteers?)
  • support multiple sorts
  • Move filter URL params from ?filters= to multiple ?f[]= params
  • Improve UI w.r.t. settings per server
  • Make it possible to export/import server settings.
  • Once 7.x-1.x is stabilized, mark 6.x-2.x as unsupported and forward/back port as appropriate to create a 6.x-3.x branch with a schema in sync with 7.x as a basis for mixed 6.x/7.x multisite search.
  • ideally, remove all facet block code and add integration with Facet API module

Comments

Additional things:

  • test suite including a basic site structure with node content, taxonomy vocabularies, etc. Could steal some code from the D6->D7 upgrade path testing.
  • strip away unused code (like maybe theme_apachesolr_breadcrumb_tid()?)
  • look at upgrade path from 6.x to 7.x branch
  • Document schema fields, changes.
  • Add general documentation to code.
  • Verify date faceting works correctly and/or if it can be improved.

Time to update or close this issue?

Perhaps we need to document this someplace else - like a g.d.o wiki page?

I'd agree it's not that useful as an issue.

Hi,

thanks a lot for the slides, they are awesome!

i'm particularly interested in the case 'I want initial searches to be targeted.'
(on Drupal 6)

in my case, the dropdown lists content types (same as 'Filter by type' facet)

i would like to pre-filter search with these content types; default is no filter

once the search results are displayed, the content type selected via the dropdown should be already selected in the facet block filter but still deselectable (as on a normal faceted search)

i also had a look on this thread: http://drupal.org/node/443986
all without success

i hope someone more experienced on Solr in Drupal can help me setting it up

thanks a lot

@miaoulafrite what does your comment have to do with this issue?

the presentation shown here:
http://www.archive.org/details/drupalconchi_day2_attain_apache_solr_codi...

and related to an aquia post lead me there

i can post a new issue if necessary but i wanted to continue the discussion related to this drupalcon presentation, where you presented very well

thanks a lot, i also read those threads, but still cannot make it happen

i'm trying to invoke hook_apachesolr_prepare_query(&$query, &$params, $caller);
-> is that already a good starting point?

i still haven't found how to link it to the search filters i defined in the dropdown with the form_alter of the search form

code provided in your presentation from DrupalCon Chicago does not work (part 'I want initial searches to be targeted.'): is it because it is for Drupal 7?

@miaoulafrite - please comment on the blog posts or open a new issue. This is not a support thread.

okay, sorry;
here is the issue: http://drupal.org/node/1168906

can you please have a look at it and provide some code valid for D6?
i'm stuck

I tagged 6.x-2.x-beta4. It's not perfect, but there hasn't been a release in a long while, a good portion of 6.x-2.x users are using the dev version currently, and all the bugs that I understand have been fixed. There are a few outstanding bugs that would take longer to fix, but I'm OK with putting out a release that contains them as long as it has no regressions.

@James - so is this the time we mark the branch as unsupported? Or we should wait until we get a 6.x-3.x into shape?

Status:Active» Fixed

I think it is effectively unsupported, so you can mark it as such.

subscribe

Are you going to make the beta4 release? I don't see it.

I don't see the link to add a release as I do in other projects. Do you mind rolling the release for me? I pushed the tag (6.x-2.0-beta4), so it should be possible to create a release.

Looks like I didn't have all the perms checked for you - you should be able to make releases now.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.