This module provides ways to index entity on solr while Update and insert . User can manage which content type want to index immediately.

Git clone url : git clone --branch 7.x-1.x https://git.drupal.org/project/apachesolr_entity_jit_index.git
Project url : https://www.drupal.org/project/apachesolr_entity_jit_index

Manual reviews of other projects

https://www.drupal.org/node/2876230#comment-12102024
https://www.drupal.org/node/2874772#comment-12103514
https://www.drupal.org/node/2874772#comment-12103530
https://www.drupal.org/node/2771203#comment-12103542

Comments

pavnish created an issue. See original summary.

PA robot’s picture

Multiple Applications
It appears that there have been multiple project applications opened under your username:

Project 1: https://www.drupal.org/node/2884075

Project 2: https://www.drupal.org/node/2878817

As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).

If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.

I'm a robot and this is an automated message from Project Applications Scraper.

PA robot’s picture

Status: Needs review » Needs work

Git clone command for the sandbox is missing in the issue summary, please add it.

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

pavnish’s picture

Issue summary: View changes
pavnish’s picture

Status: Needs work » Needs review
pavnish’s picture

Issue tags: +PAreview: review bonus
jadhavdevendra’s picture

Status: Needs review » Needs work

Git default branch is not set, see the documentation on setting a default branch.
https://pareview.sh/node/2002

pavnish’s picture

Status: Needs work » Needs review

Hi jadhavdevendra Thanks for review
I have set the default branch now

jadhavdevendra’s picture

Status: Needs review » Needs work
pavnish’s picture

Status: Needs work » Needs review

Hi jadhavdevendra

I have done the changes

ankush_03’s picture

Hi pavnish,

Please fix below issue :

1. FILE: ...t/repos/pareviewsh/pareview_temp/apachesolr_entity_jit_index.install
--------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
--------------------------------------------------------------------------
14 | ERROR | [x] Expected 1 newline at end of file; 2 found
--------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY

2. Implement hook_help() in your module file.

pavnish’s picture

Hi Ankush

I have fix these issues

ankush_03’s picture

Hi pavnish ,

I have checked above changes, it is fixed now.

mario steinitz’s picture

Status: Needs review » Needs work

No obvious coding standard issues, indeed. A minor thing to fix: Your README.txt should follow the provisions by the README Template. See https://www.drupal.org/node/2181737 .

You can review your project yourself on https://pareview.cc/pareview/https-git.drupal.org-project-apachesolr_ent...

avpaderno’s picture

Status: Needs work » Needs review

That is a minor issue. Are there other issues that need to be fixed, and they are security issues?

sleitner’s picture

Priority: Major » Normal
Status: Needs review » Needs work

Automated Review

Pareview details: https://pareview.sh/pareview/https-git.drupal.org-project-apachesolr_ent...

Review of the 7.x-1.x branch (commit fc35108):

  • Your README.txt does not follow best practices (headings need to be uppercase). See https://www.drupal.org/node/2181737 .
    • The INTRODUCTION section is missing.
    • The REQUIREMENTS section is missing.
    • The CONFIGURATION section is missing.
  • No automated test cases were found, did you consider writing Simpletests or PHPUnit tests? This is not a requirement but encouraged for professional software development.

This automated report was generated with PAReview.sh, your friendly project application review script.

Manual Review

Individual user account
Yes: Follows the guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
No: Does not follow the guidelines for in-project documentation and/or the README Template. see pareview details
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements
Coding style & Drupal API usage
no issues

The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.

If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.

This review uses the Project Application Review Template.

avpaderno’s picture

Status: Needs work » Closed (won't fix)

If you are still working on this application, you should fix all known problems and set the status to Needs review. (See also the project application workflow.)
Please don't change status of this application if you aren't sure you have time to dedicate to this application, or it will be closed again as won't fix.

I am closing this application due to lack of activity.

avpaderno’s picture

Status: Closed (won't fix) » Closed (duplicate)
Related issues: +#2878817: [D7] Commerce atom

Actually, this is a duplicate application. We accept just an application per user.