That can't really happen. While Elasticsearch was previously released under the Apache 2.0 license, it was still "owned" by Elastic.
Lucene on the other hand, is "owned" by the Apache Software Foundation (ASF). While companies can build products based on Lucene, which they release under their own choice of License, they cannot change the Lucene license itself. Only the ASF can do that.
Another example of this is Kafka. It was developed at LinkedIn, who transferred control to the ASF. When the LinkedIn employees who originally created Kafka, left to form Confluent, they had no control over the licensing of Kafka. They could only decide on the License for the Kafka add-ons that they provide. Eventually (about a year ago) they forked Kafka to create "Confluent Server", which is released under their proprietary license. Kafka itself however remains open source under Apache 2.0 license, still controlled by the ASF.
"Trust" may be too strong of a word. I would say that one should expect more consistent and predictable behavior from a foundation. I have however seen some questionable actions in the name of the ASF, where the motivations were obviously influenced by project committee members with a commercial interest.
Lucene on the other hand, is "owned" by the Apache Software Foundation (ASF). While companies can build products based on Lucene, which they release under their own choice of License, they cannot change the Lucene license itself. Only the ASF can do that.
Another example of this is Kafka. It was developed at LinkedIn, who transferred control to the ASF. When the LinkedIn employees who originally created Kafka, left to form Confluent, they had no control over the licensing of Kafka. They could only decide on the License for the Kafka add-ons that they provide. Eventually (about a year ago) they forked Kafka to create "Confluent Server", which is released under their proprietary license. Kafka itself however remains open source under Apache 2.0 license, still controlled by the ASF.