Kim: It's _always_ encouraged to create a JIRA and submit a patch. And your approach is also encouraged, first outline what you want to do to generate comments and then create a patch.
>From there you may sometimes have to prod a bit to get it applied to the code line. Do be aware that the earliest Apache release you'd see any new changes in is probably Solr 7.1. Here's some useful information about how to get started: https://wiki.apache.org/solr/HowToContribute Best, Erick On Mon, Jul 17, 2017 at 1:48 AM, Ginger (김상우) [QA and Tools] < [email protected]> wrote: > > Hi, > > I find 'parsedquery' of Solr's debug output shows human-unreadable strings > for non-string values. > > For example, "`\b\u0000\u0000\u0000\u0001" for first enum value, > "\u0001\u0000\u0000\u0000\u0000\u0000\u0000\u00007N" for a number. > > 'parsedquery' is generated at org.apache.solr.util.SolrPlugi > nUtils.doStandardQueryDebug(...). > > Modifying org.apache.lucene.index.Term and org.apache.solr.schema.FieldType > can solve the problem. > > May I try to fix it ? > > Current modification is > - Add 'externalVal' string type member variable to Term class, and new > constructor. > - Modify Term.text() to return externalVal if externalVal is not null > - Modify FieldType.getFieldQuery(...) to pass externalVal to new > constructor. > > > Thank you, > > Best regards, > > Kim Sang-woo. > > -- > > *김상우** (**진져/Ginger**)* | Measurement Platform / QA Tools Team > > 05510 서울특별시 송파구 송파대로 570 19층 > > 19F, 570, Songpa-daero, Songpa-gu, Seoul, 05510, Rep. of KOREA > > *tel*: +82 6150 5867 ｜ *fax* : +82 2 6150 5008 <+82%202-6150-5008> > > *mobile* : +82 10 4440 2357 <+82%2010-4440-2357> ｜ *e-mail* : > [email protected] > > >
