[jira] [Updated] (SOLR-9650) CloneFieldUpdateProcessorFactory doesn't preserve source fields order from configuration

2016-10-17 Thread Libor Ondrusek (JIRA) 

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

Libor Ondrusek updated SOLR-9650:
-
Priority: Minor  (was: Major)

> CloneFieldUpdateProcessorFactory doesn't preserve source fields order from 
> configuration
> 
>
> Key: SOLR-9650
> URL: https://issues.apache.org/jira/browse/SOLR-9650
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: Schema and Analysis
>Affects Versions: 6.1
>Reporter: Libor Ondrusek
>Priority: Minor
>
> We are using configuration like this:
> {code:xml}
>   
>   
> 
>   _id
>   _validFrom
>   _solrId
> 
> 
>   _solrId
>   -
> 
> 
> 
>   
> {code}
> Expected {{_solrId}} field value for document
> {code:javascript}
> {
>   "name": "Name",
>   "_validFrom": 34223040,
>   "_validTo": null,
>   "_id": "a518fad5-5421-4253-b501-0ebea0d32cd2"
> }
> {code}
> is *{{a518fad5-5421-4253-b501-0ebea0d32cd2-34223040}}*
> When HTTP REST is used, everything work fine.
> When programmatics interface using {{SolrInputDocument}} in {{SolrClient}} is 
> used value of {{_solrId}} will 
> *{{34223040-a518fad5-5421-4253-b501-0ebea0d32cd2}}* because fields are 
> composed in order from {{SolrInputDocument}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-9650) CloneFieldUpdateProcessorFactory doesn't preserve source fields order from configuration

2016-10-17 Thread Libor Ondrusek (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582146#comment-15582146
 ] 

Libor Ondrusek commented on SOLR-9650:
--

Sorry but I'm little busy for reading chats or endless mailing conversation. If 
you want take anything from my issue, take it in other case close the issue.

> CloneFieldUpdateProcessorFactory doesn't preserve source fields order from 
> configuration
> 
>
> Key: SOLR-9650
> URL: https://issues.apache.org/jira/browse/SOLR-9650
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: Schema and Analysis
>Affects Versions: 6.1
>Reporter: Libor Ondrusek
>Priority: Minor
>
> We are using configuration like this:
> {code:xml}
>   
>   
> 
>   _id
>   _validFrom
>   _solrId
> 
> 
>   _solrId
>   -
> 
> 
> 
>   
> {code}
> Expected {{_solrId}} field value for document
> {code:javascript}
> {
>   "name": "Name",
>   "_validFrom": 34223040,
>   "_validTo": null,
>   "_id": "a518fad5-5421-4253-b501-0ebea0d32cd2"
> }
> {code}
> is *{{a518fad5-5421-4253-b501-0ebea0d32cd2-34223040}}*
> When HTTP REST is used, everything work fine.
> When programmatics interface using {{SolrInputDocument}} in {{SolrClient}} is 
> used value of {{_solrId}} will 
> *{{34223040-a518fad5-5421-4253-b501-0ebea0d32cd2}}* because fields are 
> composed in order from {{SolrInputDocument}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (SOLR-9650) CloneFieldUpdateProcessorFactory doesn't preserve source fields order from configuration

2016-10-16 Thread Libor Ondrusek (JIRA) 

[ 
https://issues.apache.org/jira/browse/SOLR-9650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15581344#comment-15581344
 ] 

Libor Ondrusek commented on SOLR-9650:
--

I'm not using IRC and mailing list is very old and confused approach for 
solving issues.

My SolrJ code looks like that:
{code:java}
MapType mapType = MapType.construct(Map.class, 
SimpleType.construct(String.class), SimpleType.construct(Object.class));
List> data = 
objectMapper.readValue(resource.getInputStream(), 
CollectionType.construct(List.class, mapType));

List inputDocuments = data.stream()
.map(dataItem -> {
SolrInputDocument inputDocument = new SolrInputDocument();
dataItem.entrySet().stream().forEach(entry -> 
inputDocument.addField(entry.getKey(), entry.getValue()));
return inputDocument;
})
.collect(toList());
{code}

Data are readed from JSON file. I'm using SolrJ for that because I need 
{{EmbeddedSolrServer}} for integration testing.

> CloneFieldUpdateProcessorFactory doesn't preserve source fields order from 
> configuration
> 
>
> Key: SOLR-9650
> URL: https://issues.apache.org/jira/browse/SOLR-9650
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: Schema and Analysis
>Affects Versions: 6.1
>Reporter: Libor Ondrusek
>
> We are using configuration like this:
> {code:xml}
>   
>   
> 
>   _id
>   _validFrom
>   _solrId
> 
> 
>   _solrId
>   -
> 
> 
> 
>   
> {code}
> Expected {{_solrId}} field value for document
> {code:javascript}
> {
>   "name": "Name",
>   "_validFrom": 34223040,
>   "_validTo": null,
>   "_id": "a518fad5-5421-4253-b501-0ebea0d32cd2"
> }
> {code}
> is *{{a518fad5-5421-4253-b501-0ebea0d32cd2-34223040}}*
> When HTTP REST is used, everything work fine.
> When programmatics interface using {{SolrInputDocument}} in {{SolrClient}} is 
> used value of {{_solrId}} will 
> *{{34223040-a518fad5-5421-4253-b501-0ebea0d32cd2}}* because fields are 
> composed in order from {{SolrInputDocument}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (SOLR-9650) CloneFieldUpdateProcessorFactory doesn't preserve source fields order from configuration

2016-10-16 Thread Libor Ondrusek (JIRA) 

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

Libor Ondrusek updated SOLR-9650:
-
Description: 
We are using configuration like this:
{code:xml}
  
  

  _id
  _validFrom
  _solrId


  _solrId
  -



  
{code}

Expected {{_solrId}} field value for document
{code:javascript}
{
  "name": "Name",
  "_validFrom": 34223040,
  "_validTo": null,
  "_id": "a518fad5-5421-4253-b501-0ebea0d32cd2"
}
{code}

is *{{a518fad5-5421-4253-b501-0ebea0d32cd2-34223040}}*
When HTTP REST is used, everything work fine.
When programmatics interface using {{SolrInputDocument}} in {{SolrClient}} is 
used value of {{_solrId}} will 
*{{34223040-a518fad5-5421-4253-b501-0ebea0d32cd2}}* because fields are 
composed in order from {{SolrInputDocument}}

  was:
We are using configuration like this:
{code:xml}
  
  

  _id
  _validFrom
  _solrId


  _solrId
  -



  
{code}

Expected {{_solrId}} field value for document
{code:javascript}
{
  "name": "Name",
  "_validFrom": 34223040,
  "_validTo": null,
  "_id": "a518fad5-5421-4253-b501-0ebea0d32cd2"
}
{code}

is *{{a518fad5-5421-4253-b501-0ebea0d32cd2-34223040}}*
When HTTP REST is used, everything work fine.
When programmatics interface using {{InputSolrDocument}} in {{SolrClient}} is 
used value of {{_solrId}} will 
*{{34223040-a518fad5-5421-4253-b501-0ebea0d32cd2}}*


> CloneFieldUpdateProcessorFactory doesn't preserve source fields order from 
> configuration
> 
>
> Key: SOLR-9650
> URL: https://issues.apache.org/jira/browse/SOLR-9650
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: Schema and Analysis
>Affects Versions: 6.1
>Reporter: Libor Ondrusek
>
> We are using configuration like this:
> {code:xml}
>   
>   
> 
>   _id
>   _validFrom
>   _solrId
> 
> 
>   _solrId
>   -
> 
> 
> 
>   
> {code}
> Expected {{_solrId}} field value for document
> {code:javascript}
> {
>   "name": "Name",
>   "_validFrom": 34223040,
>   "_validTo": null,
>   "_id": "a518fad5-5421-4253-b501-0ebea0d32cd2"
> }
> {code}
> is *{{a518fad5-5421-4253-b501-0ebea0d32cd2-34223040}}*
> When HTTP REST is used, everything work fine.
> When programmatics interface using {{SolrInputDocument}} in {{SolrClient}} is 
> used value of {{_solrId}} will 
> *{{34223040-a518fad5-5421-4253-b501-0ebea0d32cd2}}* because fields are 
> composed in order from {{SolrInputDocument}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (SOLR-9650) CloneFieldUpdateProcessorFactory doesn't preserve source fields order from configuration

2016-10-16 Thread Libor Ondrusek (JIRA) 
Libor Ondrusek created SOLR-9650:


 Summary: CloneFieldUpdateProcessorFactory doesn't preserve source 
fields order from configuration
 Key: SOLR-9650
 URL: https://issues.apache.org/jira/browse/SOLR-9650
 Project: Solr
  Issue Type: Bug
  Security Level: Public (Default Security Level. Issues are Public)
  Components: Schema and Analysis
Affects Versions: 6.1
Reporter: Libor Ondrusek


We are using configuration like this:
{code:xml}
  
  

  _id
  _validFrom
  _solrId


  _solrId
  -



  
{code}

Expected {{_solrId}} field value for document
{code:javascript}
{
  "name": "Name",
  "_validFrom": 34223040,
  "_validTo": null,
  "_id": "a518fad5-5421-4253-b501-0ebea0d32cd2"
}
{code}

is *{{a518fad5-5421-4253-b501-0ebea0d32cd2-34223040}}*
When HTTP REST is used, everything work fine.
When programmatics interface using {{InputSolrDocument}} in {{SolrClient}} is 
used value of {{_solrId}} will 
*{{34223040-a518fad5-5421-4253-b501-0ebea0d32cd2}}*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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