Download & Extend
Search API » Issues

[meta] Important project announcements

Posted by drunken monkey on June 14, 2011 at 8:47pm
Project:Search API
Version:7.x-1.x-dev
Component:Miscellaneous
Category:task
Priority:minor
Assigned:Unassigned
Status:active

Issue Summary

It's been bugging me for a while that there is no good way to reach all people interested in the Search API at once. Only few will regularly scan all new issues (I think), and the project page won't be re-read that often, either.

I've tried to at least consistently tag issues with API changes lately, but a) I don't think many people are aware of that, b) I don't always think of it and c) there are sometimes other important developments that people should be aware of.

So this is a new try for such a list of announcements. People can just subscribe to this issue and I'll try to mention important issues or news here.

E.g., currently #1182614: Integrate with Facet API looks like it could bring quite a huge change to the project, and people coding for facets (or backends with facet support) should probably keep an eye on it.

Login or register to post comments

Comments

#1

Posted by drunken monkey on June 16, 2011 at 12:23pm

Also important for non-developers: #1190324: Adapt to API change in Entity API.
If you are using the dev version of Search API, you'll also need the dev version (or Beta 9) of Entity API!

#2

Posted by zambrey on June 17, 2011 at 7:44am

It is very good idea. Thanks for your work on this awesome module.
Integration with Facet API looks very promising.

#3

Posted by klausi on June 21, 2011 at 10:06am

subscribing

#4

Posted by fangel on June 21, 2011 at 12:27pm

sub.

#5

Posted by mongolito404 on June 22, 2011 at 11:32am

subscribe

#6

Posted by Akaoni on August 8, 2011 at 3:53am

Great work drunken monkey!!!
We're integrating Autonomy IDOL with our Drupal 7 site and so far Search API looks like it'll work really well for this. ;)
http://drupal.org/sandbox/Akaoni/1240206

#7

Posted by drunken monkey on July 14, 2011 at 10:32pm

See #1064884-27: Add support for indexing non-entities for a major API change looming ahead, and please help testing it!

#8

Posted by drunken monkey on July 18, 2011 at 10:05pm

Please see #1222630: [meta] Stable release for a discussion on when to create the 1.0 stable release.

#9

Posted by drunken monkey on July 24, 2011 at 11:40am

Due to the commit of #1064884: Add support for indexing non-entities, it is important to run update.php right after updating to the latest dev version of Search API!
See #1227702-1: Additional uncaught exception thrown while handling exception. for fixes if you didn't read this on time.

#10

Posted by yareckon on July 26, 2011 at 1:28pm

sub

#11

Posted by tnightingale on August 8, 2011 at 5:36pm

subscribe

#12

Posted by drunken monkey on August 14, 2011 at 9:09pm

For everyone attending the upcoming DrupalCon: I'm planning to schedule a Search API BoF there. If you are interested, you can help me find the best time slot here.

#13

Posted by drunken monkey on August 17, 2011 at 6:05pm

For those attending DrupalCon: The BoF is on, Thursday, 08/25, ~12:20 – 13:30.

#14

Posted by miiimooo on August 23, 2011 at 8:55am

subscribing

#15

Posted by drunken monkey on August 26, 2011 at 12:02pm
Title:[meta] Important developer announcements» [meta] Important project announcements

Just had a great Search API BoF yesterday and, guess what: There are new stable release blockers, yay!

#1260768: Move "Search pages" into its own project
#1260812: Move "Database search" into its own project
#1260834: Add a way to define custom data types

Comments welcome there (the last one is not very controversial, though).

#16

Posted by mollux on August 26, 2011 at 6:49pm

sub

#17

Posted by drunken monkey on August 31, 2011 at 11:00am

If you are interested in data source controllers (i.e., providing your own data types), the Search API architecture and/or integrating with external data, the following issue might be interesting for your (and your thoughts on it would be much appreciated): #1264418: Make data source controllers index-dependent.

#18

Posted by geshido on September 8, 2011 at 7:06am

sub

#19

Posted by fabsor on October 8, 2011 at 8:59pm

Subscribing

#20

Posted by drunken monkey on October 18, 2011 at 10:54am

#1308638: Reduce size of stored index settings will weed out anything from $index->options['fields'] that isn't set by the user and can't be inferred, being a not too small API change, especially for server backends.

#21

Posted by marvil07 on October 19, 2011 at 3:59am

Hey Thomas, thanks for the awesome work here. I just wanted to point you to Change records. It's a relative new way to document changes on projects at drupal.org, so maybe you would like to use it instead of this. Not sure if that's the right solution, but core is using it.

#22

Posted by drunken monkey on October 19, 2011 at 9:33am

Thanks for linking to the documentation, I couldn't for the life of me find that! I was already aware of the feature though. However, as it seems there isn't a way to subscribe to change records (please correct me if I'm wrong) I still found this approach more practical.
Furthermore, this also allows to notify people of changes before they occur, giving them the opportunity to discuss or help with them. Also, pointers to other discussions or important issues/pages are possible this way.

#23

Posted by marvil07 on October 20, 2011 at 5:55am

Right, there is no way to follow change notices, but IMHO it's a great to document API changes, because it's easier to filter them based on version string(i.e. on drupal project changes introduced in 7.6). Naturally, this issue have other target, announcements, and it just works(tm) for it :-)

Anyway, just a suggestion, what works for you is fine ;-).

#24

Posted by drunken monkey on November 3, 2011 at 1:40pm

Remembered another stable release blocker: #1330506: Remove the old Facets module.
I guess this should be done before a stable release. If you don't think so, please comment there.

However, on the plus side we are almost down to zero in the blocker list (#1308638: Reduce size of stored index settings is just open for non-blocking follow-ups and the others could be committed right away) so there's almost definitely gonna be an RC this week.
Finally.

#25

Posted by keithyau on November 18, 2011 at 5:18am

Subscribe

#26

Posted by scotjam on November 18, 2011 at 9:48am

sub

#27

Posted by fangel on November 18, 2011 at 10:01am

Keithyau and Scotjam: It's now possible to subscribe without posting a comment. Just hit the big green "Follow" button at the top right of the issue.

#28

Posted by scotjam on November 18, 2011 at 10:04am

oops! thanks for pointing that out.

#29

Posted by drunken monkey on May 1, 2012 at 10:16am

Please help me with my (hopefully happening) DrupalCon session: #1555808: Brainstorming for my DrupalCon session.

#30

Posted by drunken monkey on May 19, 2012 at 10:29am

#1528436: Support exportable entity types will change the stored data type of entity references if the entity in question uses string keys for identification (e.g., most exportables). Those were broken before, so if you didn't have any problems, this won't affect your site.
However, module maintainers might want to check their modules whether they make that assumption (entity key = integer) anywhere currently.

Also, additional testers would of course be welcome.

#31

Posted by drunken monkey on July 6, 2012 at 8:55pm

Please see, read and (if you have an opinion or some arguments) comment on #1390598: Add a way to easily identify facet filters inside the query, which contains a small API change/addition (which would probably mostly only affect maintainers of service classes).

#32

Posted by drunken monkey on July 29, 2012 at 1:11pm

If you're coming to DrupalCon Munich, you might be interested in these:

#33

Posted by drunken monkey on March 19, 2013 at 8:44pm

Not relevant to the Search API in general, but important enough for all Solr users, I guess: in #1846254: Remove the SolrPhpClient dependency I aim to finally remove the SolrPhpClient dependency from the module and thus get it (finally!) ready for a stable release. Please help by testing any functionality you are using (or more, if you want to)!

#34

Posted by drunken monkey on March 27, 2013 at 10:28am

Especially important for maintainers of service classes: #1783746: Add support for "between" operator would add – the title probably gives it away – a between operator for use in Search API queries. This is necessary as combining >= and <= leads to unexpected/undesired results for multi-valued fields, thus constricting functionality.
I'd love to get this in, but it would be an API change, or at least add a feature. So please keep this on your radar, and provide feedback if possible.

Two other issues which would introduce (almost completely backwards-compatible) API changes are #1760706: Add a flexible way for determining whether an index contains entities and #1720348: Add the concept of query extenders. These could also use some additional eyes, or hands.

#35

Posted by drunken monkey on March 28, 2013 at 2:49pm

Just realized that, since #1783746: Add support for "between" operator also changes the filter handlers of the Search API Views module, developers who have written their own filter handlers based on those might be affected, too. I tried to mitigate that in my revision of the patch, but please see, review and test yourself, and possibly prepare to update your own code accordingly.