Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Search] Propagate search-specific configuration to Search service #460

Open
magento-engcom-team opened this issue Dec 8, 2020 · 9 comments · May be fixed by magento/storefront-search-ce#7
Assignees

Comments

@magento-engcom-team
Copy link

Need to propagate search-specific configuration to Search service

AC:

  • Add new "ImportConfig" method to Search Service
  • Add search-specific configuration in message-broker
  • Use imported configuration inside Search service instead of hard-coded config values
    • \Magento\SearchStorefrontStub\Model\Search\Options and other places

Proto schema:

service Search {
  rpc ImportConfig (ImportConfigRequest) returns (ImportConfigResponse)  {}
}

message GetConfigRequest {
  repeated string name = 1;
}

message ImportConfigRequest {
  repeated Config config = 1;
}

message ImportConfigResponse {
  bool status = 1;
  string message = 2;
}

message Config {
  string name = 1;
  string value = 2;
}

 

@magento-engcom-team
Copy link
Author

The issue was exported from the internal JIRA. The link to the original JIRA issue: https://jira.corp.magento.com/browse/SFAPP-175

@m2-assistant
Copy link

m2-assistant bot commented Dec 8, 2020

Hi @magento-engcom-team. Thank you for your report.
To help us process this issue please make sure that you provided sufficient information.

Please, add a comment to assign the issue: @magento I am working on this


@mslabko mslabko changed the title Propagate search-specific configuration to Search service [Search] Propagate search-specific configuration to Search service Dec 8, 2020
@lykhachov
Copy link
Contributor

required config paths are:
'catalog/layered_navigation/price_range_calculation'
'catalog/layered_navigation/interval_division_limit'
'catalog/layered_navigation/price_range_step'
'catalog/layered_navigation/price_range_max_intervals'
'catalog/layered_navigation/one_price_interval'

desired config are:
Magento Elasticsearch connection config

@RuslanKostiv1
Copy link
Contributor

RuslanKostiv1 commented Dec 14, 2020

@lykhachov @mslabko
Should store node be in message Config for search service?
It's present in proto scheme here

        message Config {
          string name = 1;
          string value = 2;
          string store = 3;
        }

@nihara47
Copy link

@magento I am working on this

@lykhachov
Copy link
Contributor

I suppose yes, as we have store node in the search request

@nihara47
Copy link

nihara47 commented Jan 19, 2021

@RuslanKostiv1 I have provided a PR for addition of new "importconfig" method for search service
magento/storefront-search-ce#7
Please suggest if any changes on that, Thank you
@lykhachov

@nihara47
Copy link

required config paths are:
'catalog/layered_navigation/price_range_calculation'
'catalog/layered_navigation/interval_division_limit'
'catalog/layered_navigation/price_range_step'
'catalog/layered_navigation/price_range_max_intervals'
'catalog/layered_navigation/one_price_interval'

desired config are:
Magento Elasticsearch connection config

@lykhachov @RuslanKostiv1 Can you provide me some insights as where I will add these config paths
As I understand we need to declare and map those inside etc/configuration_import_mapping.xml but in which module to use these imported configuration inside Search services

@mslabko
Copy link
Member

mslabko commented Feb 5, 2021

Hey @nihara47 , thank you for your contribution! I will try to check your PR next week

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants