[
https://issues.apache.org/jira/browse/SOLR-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839566#comment-16839566
]
Yonik Seeley commented on SOLR-13437:
-------------------------------------
I'm fine with forking... I haven't had a chance to do anything with noggit
recently.
It might make things easier to keep the same namespace though (for anyone in
Solr who uses the noggit APIs directly)
> fork noggit code to Solr
> ------------------------
>
> Key: SOLR-13437
> URL: https://issues.apache.org/jira/browse/SOLR-13437
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We rely on noggit for all our JSON encoding/decoding needs.The main project
> is not actively maintained . We cannot easily switch to another parser
> because it may cause backward incompatibility and we have advertised the
> ability to use flexible JSON and we also use noggit internally in many classes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
