subject:"\[jira\] \[Updated\] \(SOLR\-6051\) Field names beginning with numbers give different and incorrect results depending on placement in URL query"

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

2014-05-19 Thread Shawn Heisey (JIRA)


 [ 
https://issues.apache.org/jira/browse/SOLR-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shawn Heisey updated SOLR-6051:
---

Fix Version/s: 4.9

 Field names beginning with numbers give different and incorrect results 
 depending on placement in URL query
 ---

 Key: SOLR-6051
 URL: https://issues.apache.org/jira/browse/SOLR-6051
 Project: Solr
  Issue Type: Bug
  Components: documentation
Affects Versions: 4.7.2
 Environment: CentOS 6+
Reporter: Mark Ebbert
Priority: Minor
  Labels: documentation, patch
 Fix For: 4.9


 I've looked all over for specific field name requirements and can't find any 
 official documentation. Is there official documentation on field names? If 
 not, *please* provide some! 
 We created several field names that begin with numbers, but SOLR doesn't seem 
 to handle that well. Here are two identical URL queries that produce 
 different output:
 {quote}
 http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq
 {quote}
 and 
 {quote}
 http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq
 {quote}
 The only difference between the two queries is the location of '1000G_freq' 
 (middle vs. end). The first query does not return the 1000G_freq value but 
 the second does. Additionally, both return a value that does not exist 
 (1000:1000). Seems to be doing something funky with the 1000 in the field 
 name. The 1000:1000 disappears if I remove '1000G_freq' from the query.
 Here are the outputs from both queries:
 h2. Query 1 Results
 {code:title=Query 1 Results|borderStyle=solid}
 {
   responseHeader:{
 status:0,
 QTime:1,
 params:{
   fl:chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq,
   q:chr:19 AND pos:1101}},
   response:{numFound:5,start:0,docs:[
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000}]
   }}
 {code}
 h2. Query 2 Results
 {code:title=Query 2 Results|borderStyle=solid}
 {
   responseHeader:{
 status:0,
 QTime:0,
 params:{
   fl:chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq,
   q:chr:19 AND pos:1101}},
   response:{numFound:5,start:0,docs:[
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000G_freq:0.43,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000G_freq:0.43,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000}]
   }}
 {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

2014-05-16 Thread Ahmet Arslan (JIRA)


 [ 
https://issues.apache.org/jira/browse/SOLR-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ahmet Arslan updated SOLR-6051:
---

Component/s: documentation

 Field names beginning with numbers give different and incorrect results 
 depending on placement in URL query
 ---

 Key: SOLR-6051
 URL: https://issues.apache.org/jira/browse/SOLR-6051
 Project: Solr
  Issue Type: Bug
  Components: documentation
Affects Versions: 4.7.2
 Environment: CentOS 6+
Reporter: Mark Ebbert
Priority: Minor
  Labels: documentation, patch

 I've looked all over for specific field name requirements and can't find any 
 official documentation. Is there official documentation on field names? If 
 not, *please* provide some! 
 We created several field names that begin with numbers, but SOLR doesn't seem 
 to handle that well. Here are two identical URL queries that produce 
 different output:
 {quote}
 http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq
 {quote}
 and 
 {quote}
 http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq
 {quote}
 The only difference between the two queries is the location of '1000G_freq' 
 (middle vs. end). The first query does not return the 1000G_freq value but 
 the second does. Additionally, both return a value that does not exist 
 (1000:1000). Seems to be doing something funky with the 1000 in the field 
 name. The 1000:1000 disappears if I remove '1000G_freq' from the query.
 Here are the outputs from both queries:
 h2. Query 1 Results
 {code:title=Query 1 Results|borderStyle=solid}
 {
   responseHeader:{
 status:0,
 QTime:1,
 params:{
   fl:chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq,
   q:chr:19 AND pos:1101}},
   response:{numFound:5,start:0,docs:[
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000}]
   }}
 {code}
 h2. Query 2 Results
 {code:title=Query 2 Results|borderStyle=solid}
 {
   responseHeader:{
 status:0,
 QTime:0,
 params:{
   fl:chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq,
   q:chr:19 AND pos:1101}},
   response:{numFound:5,start:0,docs:[
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000G_freq:0.43,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000G_freq:0.43,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000}]
   }}
 {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

2014-05-15 Thread Mark Ebbert (JIRA)


 [ 
https://issues.apache.org/jira/browse/SOLR-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Ebbert updated SOLR-6051:
--

Description: 
I've looked all over for specific field name requirements and can't find any 
official documentation. Is there official documentation on field names? If not, 
*please* provide some! 

We created several field names that begin with numbers, but SOLR doesn't seem 
to handle that well. Here are two identical URL queries that produce 
different output:

{quote}
http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq
{quote}

and 

{quote}
http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq
{quote}

The only difference between the two queries is the location of '1000G_freq' 
(middle vs. end). The first query does not return the 1000G_freq value but the 
second does. Additionally, both return a value that does not exist 
(1000:1000). Seems to be doing something funky with the 1000 in the field 
name. The 1000:1000 disappears if I remove '1000G_freq' from the query.

Here are the outputs from both queries:

h2. Query 1 Results
{code:title=Query 1 Results|borderStyle=solid}
{
  responseHeader:{
status:0,
QTime:1,
params:{
  fl:chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq,
  q:chr:19 AND pos:1101}},
  response:{numFound:5,start:0,docs:[
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000}]
  }}
{code}

h2. Query 2 Results
{code:title=Query 2 Results|borderStyle=solid}
{
  responseHeader:{
status:0,
QTime:0,
params:{
  fl:chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq,
  q:chr:19 AND pos:1101}},
  response:{numFound:5,start:0,docs:[
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000G_freq:0.43,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000G_freq:0.43,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000}]
  }}
{code}

  was:
I've looked all over for specific field name requirements and can't find any 
official documentation. Is there official documentation on field names? If not, 
*please* provide some! 

We created several field names that begin with numbers, but SOLR doesn't seem 
to handle that well. Here are two identical URL queries that produce 
different output:

{quote}
http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq
{quote}

and 

{quote}
http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq
{quote}

The only difference between the two queries is the location of '1000G_freq' 
(middle vs. end). The first query does not return the 1000G_freq value but the 
second does. Additionally, both return a value (1000:1000) that does not 
exist. Seems to be doing something funky with the 1000 in the field name. The 
1000:1000 disappears if I remove the '1000G_freq' from the query.

Here are the outputs from both queries:

h2. Query 1 Results
{code:title=Query 1 Results|borderStyle=solid}
{
  responseHeader:{
status:0,
QTime:1,
params:{
  fl:chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq,
  q:chr:19 AND pos:1101}},
  response:{numFound:5,start:0,docs:[
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000}]
  }}
{code}

h2. Query 2 Results
{code:title=Query 2 Results|borderStyle=solid}
{
  responseHeader:{
status:0,
QTime:0,
params:{

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

2014-05-12 Thread Mark Ebbert (JIRA)


 [ 
https://issues.apache.org/jira/browse/SOLR-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Ebbert updated SOLR-6051:
--

Description: 
I've looked all over for specific field name requirements and can't find any 
official documentation. Is there official documentation on field names? If not, 
*please* provide some! 

We created several field names that begin with numbers, but SOLR doesn't seem 
to handle that well. Here are two identical URL queries that produce 
different output:

{quote}
http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq
{quote}

and 

{quote}
http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq
{quote}

The only difference between the two queries is the location of '1000G_freq' 
(middle vs. end). The first query does not return the 1000G_freq value but the 
second does. Additionally, both return a value (1000:1000) that does not 
exist. Seems to be doing something funky with the 1000 in the field name. The 
1000:1000 disappears if I remove the '1000G_freq' from the query.

Here are the outputs from both queries:

h2. Query 1 Results
{code:title=Query 1 Results|borderStyle=solid}
{
  responseHeader:{
status:0,
QTime:1,
params:{
  fl:chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq,
  q:chr:19 AND pos:1101}},
  response:{numFound:5,start:0,docs:[
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000}]
  }}
{code}

h2. Query 2 Results
{code:title=Query 2 Results|borderStyle=solid}
{
  responseHeader:{
status:0,
QTime:0,
params:{
  fl:chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq,
  q:chr:19 AND pos:1101}},
  response:{numFound:5,start:0,docs:[
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000G_freq:0.43,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000G_freq:0.43,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000}]
  }}
{code}

  was:
I've looked all over for specific field name requirements and can't find any 
official documentation. Is there official documentation on field names? If not, 
*please* provide some! 

We created several field names that begin with numbers, but SOLR doesn't seem 
to handle that well. Here are two identical URL queries that produce 
different output:

{quote}
http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq
{quote}

and 

{quote}
http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq
{quote}

The only difference between the two queries is the location of '1000G_freq' 
(middle vs. end). The first query does not return the 1000G_freq value and the 
second does. Additionally, both return a value (1000:1000) that does not 
exist. Seems to be doing something funky with the 1000 in the field name. The 
1000:1000 disappears if I remove the '1000G_freq' from the query.

Here are the outputs from both queries:

h2. Query 1 Results
{code:title=Query 1 Results|borderStyle=solid}
{
  responseHeader:{
status:0,
QTime:1,
params:{
  fl:chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq,
  q:chr:19 AND pos:1101}},
  response:{numFound:5,start:0,docs:[
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
AFR_freq:0.05,
ASN_freq:0.55,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000},
  {
chr:19,
pos:1101,
ref:G,
alt:C,
1000:1000}]
  }}
{code}

h2. Query 2 Results
{code:title=Query 2 Results|borderStyle=solid}
{
  responseHeader:{
status:0,
QTime:0,
params:{

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

2014-05-10 Thread Mark Ebbert (JIRA)


 [ 
https://issues.apache.org/jira/browse/SOLR-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Ebbert updated SOLR-6051:
--

Priority: Minor  (was: Major)

 Field names beginning with numbers give different and incorrect results 
 depending on placement in URL query
 ---

 Key: SOLR-6051
 URL: https://issues.apache.org/jira/browse/SOLR-6051
 Project: Solr
  Issue Type: Bug
Affects Versions: 4.7.2
 Environment: CentOS 6+
Reporter: Mark Ebbert
Priority: Minor
  Labels: documentation, patch

 I've looked all over for specific field name requirements and can't find any 
 official documentation. Is there official documentation on field names? If 
 not, *please* provide some! 
 We created several field names that begin with numbers, but SOLR doesn't seem 
 to handle that well. Here are two identical URL queries that produce 
 different output:
 {quote}
 http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq
 {quote}
 and 
 {quote}
 http://our_server:8080/solr/query?q=chr:19%20AND%20pos:1101fl=chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq
 {quote}
 The only difference between the two queries is the location of '1000G_freq' 
 (middle vs. end). The first query does not return the 1000G_freq value but 
 the second does. Additionally, both return a value that does not exist 
 (1000:1000). Seems to be doing something funky with the 1000 in the field 
 name. The 1000:1000 disappears if I remove '1000G_freq' from the query.
 Here are the outputs from both queries:
 h2. Query 1 Results
 {code:title=Query 1 Results|borderStyle=solid}
 {
   responseHeader:{
 status:0,
 QTime:1,
 params:{
   fl:chr,pos,ref,alt,1000G_freq,AFR_freq,ASN_freq,
   q:chr:19 AND pos:1101}},
   response:{numFound:5,start:0,docs:[
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000}]
   }}
 {code}
 h2. Query 2 Results
 {code:title=Query 2 Results|borderStyle=solid}
 {
   responseHeader:{
 status:0,
 QTime:0,
 params:{
   fl:chr,pos,ref,alt,AFR_freq,ASN_freq,1000G_freq,
   q:chr:19 AND pos:1101}},
   response:{numFound:5,start:0,docs:[
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000G_freq:0.43,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000G_freq:0.43,
 AFR_freq:0.05,
 ASN_freq:0.55,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000},
   {
 chr:19,
 pos:1101,
 ref:G,
 alt:C,
 1000:1000}]
   }}
 {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

[jira] [Updated] (SOLR-6051) Field names beginning with numbers give different and incorrect results depending on placement in URL query

5 matches

Site Navigation

Mail list logo

Footer information